git2go

Author SHA1 Message Date

Author	SHA1	Message	Date
lhchavez	84b7f45673	Add the version number to go.mod This is the second take on trying to tag the current release with a Go version. (cherry picked from commit `a32375a860`)	2020-08-16 07:19:20 -07:00
lhchavez	7694d5f5fc	Add the /v28 suffix to go.mod This is compliant with https://github.com/golang/go/wiki/Modules#releasing-modules-v2-or-higher, which says ``` Major branch: Update the go.mod file to include a /v3 at the end of the module path in the module directive (e.g., module github.com/my/module/v3). Update import statements within the module to also use /v3 (e.g., import "github.com/my/module/v3/mypkg"). Tag the release with v3.0.0. ``` This also means that unfortunately we cannot keep using libgit2's exact version number (plus a build number for git2go purposes, since go only recognizes vMAJOR.MINOR.PATCH format). (Tentatively) fixes: #536	2020-02-18 19:50:49 -08:00
lhchavez	30c57ff09e	Add support for Go 1.11 modules This change adds a `go.mod` file. An empty file is sufficient since this project has no external dependencies. For people that want to use the static version of libgit2, this module can be vendored and the following can be added to their `go.mod` file: replace github.com/libgit2/git2go => ./vendor/github.com/libgit2/git2go	2019-01-06 07:34:50 -08:00

lhchavez

84b7f45673

Add the version number to go.mod

This is the second take on trying to tag the current release with a Go
version.

(cherry picked from commit a32375a860)

2020-08-16 07:19:20 -07:00

lhchavez

7694d5f5fc

Add the /v28 suffix to go.mod

This is compliant with
https://github.com/golang/go/wiki/Modules#releasing-modules-v2-or-higher,
which says

```
Major branch: Update the go.mod file to include a /v3 at the end of the
module path in the module directive (e.g., module
github.com/my/module/v3). Update import statements within the module to
also use /v3 (e.g., import "github.com/my/module/v3/mypkg"). Tag the
release with v3.0.0.
```

This also means that unfortunately we cannot keep using libgit2's exact
version number (plus a build number for git2go purposes, since go only
recognizes vMAJOR.MINOR.PATCH format).

(Tentatively) fixes: #536

2020-02-18 19:50:49 -08:00

lhchavez

30c57ff09e

Add support for Go 1.11 modules

This change adds a `go.mod` file. An empty file is sufficient since this
project has no external dependencies. For people that want to use the static
version of libgit2, this module can be vendored and the following can be added
to their `go.mod` file:

    replace github.com/libgit2/git2go => ./vendor/github.com/libgit2/git2go

2019-01-06 07:34:50 -08:00

3 Commits