rugged
rugged copied to clipboard
libgit2
ruby bindings to libgit2
I use walker find a commit but when i get it`s diff, i think the result is wrong. rugged/lib/rugged/commit.rb ``` def diff(*args) args.unshift(parents.first) if args.size == 1 && args.first.is_a?(Hash) self.tree.diff(*args)...
libgit2 already supports ssh keys from memory (https://libgit2.org/libgit2/#HEAD/group/cred/git_cred_ssh_key_memory_new), just need to wrap that with a suitable ruby object
```ruby repo = Rugged::Repository.new("") repo.submodules.each{}; nil # segfaults ``` I've reproed on Mac and Linux, both times _not_ using the system libgit2.
Would it be possible to pull in https://github.com/libgit2/libgit2/blob/master/src/describe.c - aka https://github.com/libgit2/libgit2/pull/2592/ so that rugged could support easy version data on proprly tagged repos.
Rugged doesn't seem to aknowledge `core.attributesFile` (falling back to `$HOME/.config/git/attributes`) or `$(prefix)/etc/gitattributes` as specified in [the docs](https://git-scm.com/docs/gitattributes) when fetching attributes for a path with `repo.fetch_attributes(path)`. `git check-attr` handles that so...
This looks like a regression from libgit2 0.28.0, but I'm not sure yet if it's a Rugged issue or a libgit2 one. Here's a sample reproduction: ```ruby require 'rugged' repo...
Almost all of the string used inside a git repository are encoding unaware. This includes things like refnames, commit metadata, path names, and a lot more. The exception is commit...
are there any changes expected/needed or should it just work? looks to me the check in extconf.rb was just too pessimistic
I've been trying to get this to work on travis. I finally got this to work: https://github.com/kurocha/teapot/blob/4ad7ae859bbff1a46744406634cf852dd5286ac2/.travis.yml#L16-L19 But, is there something simpler? Without using RUGGED_USE_SYSTEM_LIBRARIES=y it would fail but I...
The Windows build has been [broken](https://github.com/libgit2/rugged/issues/612) multiple [times](https://github.com/libgit2/rugged/issues/669) already, so probably adding CI on Windows via [AppVeyor](https://www.appveyor.com/) in addition to Travis CI is a good idea. Apparently that was @arthurschreiber's...
