Add possibiliy of checkout on specific path
1 file changed
tree: 2692c6b86b39750c6062d1501189beb4bffa1cf5
  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. clone.go
  13. clone_test.go
  14. commit.go
  15. config.go
  16. credentials.go
  17. diff.go
  18. diff_test.go
  19. git.go
  20. git_test.go
  21. graph.go
  22. index.go
  23. index_test.go
  24. LICENSE
  25. Makefile
  26. merge.go
  27. merge_test.go
  28. note.go
  29. note_test.go
  30. object.go
  31. object_test.go
  32. odb.go
  33. odb_test.go
  34. packbuilder.go
  35. patch.go
  36. patch_test.go
  37. push_test.go
  38. README.md
  39. refdb.go
  40. reference.go
  41. reference_test.go
  42. remote.go
  43. remote_test.go
  44. repository.go
  45. revparse.go
  46. revparse_test.go
  47. settings.go
  48. settings_test.go
  49. status.go
  50. status_test.go
  51. submodule.go
  52. submodule_test.go
  53. tag.go
  54. tag_test.go
  55. tree.go
  56. walk.go
  57. wrapper.c
README.md

git2go

GoDoc Build Status

Go bindings for libgit2. The master branch follows the latest libgit2 release. The versioned branches indicate which libgit2 version they work against.

Installing

This project needs libgit2, which is written in C so we need to build that as well. In order to build libgit2, you need cmake, pkg-config and a C compiler. You will also need the development packages for OpenSSL and LibSSH2 installed if you want libgit2 to support HTTPS and SSH respectively.

Stable version

git2go has versioned branches which indicate which version of libgit2 they work against. Install the development package it on your system via your favourite package manager or from source and you can use a service like gopkg.in to use the appropriate version. For the libgit2 v0.22 case, you can use

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

to use a version of git2go which will work against libgit2 v0.22 and dynamically link to the library.

From master

The master branch follows libgit2's master branch, which means there is no stable API or ABI to link against. git2go can statically link against a vendored version of libgit2.

Run go get -d github.com/libgit2/git2go to download the code and go to your $GOPATH/src/github.com/libgit2/git2go dir. 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 and run go install such that it's statically linked to the git2go package.

Paralellism and network operations

libgit2 uses 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 master branch, similarly to installing, running the tests requires linking against the local libgit2 library, so the Makefile provides a wrapper

make test

alternatively, if you want to pass arguments to go test, you can use the script that sets it all up

./script/with-static.sh go test -v

which will run the specified arguments with the correct environment variables.

License

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

Authors

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