jcarr/git2go/README.md, branch v0.0.35

update to libgit2 version 1.8.4. dump old github and vendor stuff

2024-12-16T23:50:57Z

go install go.wit.com/apps/go-clone@latest go install go.wit.com/apps/go-mod-clean@latest go-clone --recusive go.wit.com/lib/git2go Signed-off-by: Jeff Carr

libgit2 v1.5.0 #major (#929)

2022-10-04T14:50:57Z

Update libgit2 to v1.5.0. Replace `SmartProxyOptions()` with `SmartRemoteConnectOptions()`. Fixes: https://github.com/libgit2/git2go/issues/899 Signed-off-by: Sanskar Jaiswal Co-authored-by: lhchavez

readme: link to godoc for current main branch (#886)

2022-01-23T01:54:04Z

The GoDoc link currently refers to the initial version of this package, but usually folks are looking for whatever matches the current main branch. This should be updated whenever the package version changes.

Fix replace statement example in README.md (#859)

2021-11-08T14:02:36Z

libgit2 v1.3.0 #major (#840)

2021-10-14T11:42:42Z

This commit introduces libgit2 v1.3.0 to git2go, which brings a large number of [bugfixes and features](https://github.com/libgit2/libgit2/releases/tag/v1.3.0). This also marks the start of the v33 release.

libgit2 v1.2.0 #major

2021-09-06T01:52:01Z

This commit introduces libgit2 v1.2.0 to git2go, which brings a large number of [bugfixes and features](https://github.com/libgit2/libgit2/releases/tag/v1.2.0). This also marks the start of the v32 release.

Rename the default branch to `main` (#786)

2021-09-04T20:33:34Z

We've renamed the default branch from `master` to `main`, so we need to change a bunch of references to that.

Create v31 to support libgit2 v1.1.x (#668)

2020-10-27T01:09:26Z

The libgit2 `v1.1.0` is released two weeks ago. This PR allows `git2go` to link against the new version.

Refresh the GitHub Actions CI (#632)

2020-08-16T00:19:53Z

This change: * Builds the library with Go 1.14, too. * Builds the non-legacy tests with Ubuntu Focal (20.04). * Adds testing for system-wide libraries, both static and dynamic versions. * Fixes a typo in the README.

Revamp the ways in which the library can be built (#621)

2020-06-21T22:40:52Z

This change allows to link the system version of libgit2 statically. Since `-tags static` is already used for the bundled version of the library and to avoid breaking old workflows, `-tags static,system_libgit2` is now used to select that. This means that the valid combinations are: | Flag | Effect | |-------------------------------|-----------------------------------------------| | _No flags_ | Dynamically-linked against the system libgit2 | | `-tags static,system_libgit2` | Statically-linked against the system libgit2 | | `-tags static` | Statically-linked against the bundled libgit2 | Note that there is no way to express dynamically linking against the bundled libgit2 because that makes very little sense, since the binaries wouldn't be able to be distributed. If that's still desired, the `PKG_CONFIG_PATH` environment variable can set before building the code. [`Makefile`](https://github.com/libgit2/git2go/blob/master/Makefile) has an example of how it is used in the CI.