Update git_dynamic.go

this branch should support libgit2 v0.26.0
1 file changed
tree: a4ced8f16b4025af869170e7735ff8806921390f
  1. script/
  2. vendor/
  3. .gitmodules
  4. .travis.yml
  5. blame.go
  6. blame_test.go
  7. blob.go
  8. blob_test.go
  9. branch.go
  10. branch_test.go
  11. checkout.go
  12. cherrypick.go
  13. cherrypick_test.go
  14. clone.go
  15. clone_test.go
  16. commit.go
  17. config.go
  18. config_test.go
  19. credentials.go
  20. describe.go
  21. describe_test.go
  22. diff.go
  23. diff_test.go
  24. features.go
  25. git.go
  26. git_dynamic.go
  27. git_static.go
  28. git_test.go
  29. graph.go
  30. handles.go
  31. ignore.go
  32. index.go
  33. index_test.go
  35. Makefile
  36. merge.go
  37. merge_test.go
  38. note.go
  39. note_test.go
  40. object.go
  41. object_test.go
  42. odb.go
  43. odb_test.go
  44. packbuilder.go
  45. patch.go
  46. patch_test.go
  47. push_test.go
  48. README.md
  49. rebase.go
  50. rebase_test.go
  51. refdb.go
  52. reference.go
  53. reference_test.go
  54. remote.go
  55. remote_test.go
  56. repository.go
  57. reset.go
  58. reset_test.go
  59. revparse.go
  60. revparse_test.go
  61. settings.go
  62. settings_test.go
  63. signature.go
  64. stash.go
  65. stash_test.go
  66. status.go
  67. status_test.go
  68. submodule.go
  69. submodule_test.go
  70. tag.go
  71. tag_test.go
  72. tree.go
  73. tree_test.go
  74. walk.go
  75. wrapper.c


GoDoc Build Status

Go bindings for libgit2.

Which branch to use

The numbered branches work against the version of libgit2 as specified by their number. You can import them in your project via gopkg.in, e.g. if you have libgit2 v0.25 installed you'd import with

import "gopkg.in/libgit2/git2go.v25"

which will ensure there are no sudden changes to the API.

The master branch follows the tip of libgit2 itself (with some lag) and as such has no guarantees on its own API nor does it have expectations the stability of libgit2's. Thus this only supports statically linking against libgit2.


This project wraps the functionality provided by libgit2. It thus needs it in order to perform the work.

This project wraps the functionality provided by libgit2. If you‘re using a versioned branch, install it to your system via your system’s package manager and then install git2go.

Versioned branch, dynamic linking

When linking dynamically against a released version of libgit2, install it via your system's package manager. CGo will take care of finding its pkg-config file and set up the linking. Import via gopkg.in, e.g. to work against libgit2 v0.25

import "gopkg.in/libgit2/git2go.v25"

Master branch, or static linking

If using master or building a branch statically, we need to build libgit2 first. In order to build it, you need cmake, pkg-config and a C compiler. You will also need the development packages for OpenSSL (outside of Windows or macOS) and LibSSH2 installed if you want libgit2 to support HTTPS and SSH respectively. Note that even if libgit2 is included in the resulting binary, its dependencies will not be.

Run go get -d github.com/libgit2/git2go to download the code and go to your $GOPATH/src/github.com/libgit2/git2go directory. From there, we need to build the C code and put it into the resulting go binary.

git submodule update --init # get libgit2
make install

will compile libgit2, link it into git2go and install it.

Parallelism and network operations

libgit2 may use OpenSSL and LibSSH2 for performing encrypted network connections. For now, git2go asks libgit2 to set locking for OpenSSL. This makes HTTPS connections thread-safe, but it is fragile and will likely stop doing it soon. This may also make SSH connections thread-safe if your copy of libssh2 is linked against OpenSSL. Check libgit2's THREADSAFE.md for more information.

Running the tests

For the stable version, go test will work as usual. For the next branch, similarly to installing, running the tests requires building a local libgit2 library, so the Makefile provides a wrapper that makes sure it's built

make test

Alternatively, you can build the library manually first and then run the tests

go test -v


M to the I to the T. See the LICENSE file if you've never seen a MIT license before.


  • Carlos Martín (@carlosmn)
  • Vicent Martí (@vmg)