grit
grit copied to clipboard
gitlabhq
Grit gives you object oriented read/write access to Git repositories via Ruby. Patched for GitLab
If you have the following in your `~/.gitconfig`, `Grit::Repo.log()` will break. ```gitconfig [color] ui = always ``` To reproduce: ```ruby require_relative "lib/grit.rb" Grit.debug = true repo = Grit::Repo.new("test/dot_git", :is_bare =>...
Just a friendly note to passers-by that GitLab, who originally forked 'grit' to 'gitlab-grit' in order to maintain it, has since switched to the 'rugged' gem. https://twitter.com/gitlab/status/431428479469748225 https://github.com/gitlabhq/gitlab_git#moved-from-grit-to-rugged https://github.com/mojombo/grit/issues/188#issuecomment-112919437 And...
Allow empty emails when parsing the commit message. Empty emails can be set by `git config user.email `.
Updated Grit::Commit#diffs method to honor options received in the parameter when calculating diffs.
I am not a ruby expert, but it seems to me that options passed to diffs method are not honored when diffs are calculated. Am I missing something? I came...
This is an error that I have encountered a lot while setting up development VMs with Vagrant to use a technology stack that includes gitlab-grit: http://f.cl.ly/items/1G3H0F0X0P0S2P091W04/vagrantvaultwikivagrant$%20rake%20.txt That error is really...
I add instance method to get path of blob and tree (and also add method to get repo) # Usage ### Blob You can get current blob path with `@blob.path`...
Handle encoding header of Git commits when possible.
Added /^--\n/ to line 724 instead of "--\n" This caused errors, when in the file to be grepped a "--\n" string was present as in markdown files used for Headings
### Bug Return wrong blob object when `repo.diff` like this ``` ruby repo = Grit::Repo.new(".") head = repo.commits.first base = repo.commits.last blob = repo.diff(base, head).first.b_blob # => # ``` ###...