search

gitlabhq / grit

Grit gives you object oriented read/write access to Git repositories via Ruby. Patched for GitLab
gitlab.org
MIT License
59 stars 55 forks source link

WIP: gitlab-grit gem to replace grit fork #20

Closed dzaporozhets closed 11 years ago

coveralls commented 11 years ago

Coverage Status

Coverage decreased (-0%) when pulling c4e5bef0b4bb986b6329b66a19ba7394c0a6e5ab on gitlab-grit-gem into e873bb84ac3c4f8249311490d6a7c6ac9127625f on master.

coveralls commented 11 years ago

Coverage Status

Coverage remained the same when pulling f24bd3868850c6cbafab84a39bd3973e9d3e9a99 on gitlab-grit-gem into e873bb84ac3c4f8249311490d6a7c6ac9127625f on master.

coveralls commented 11 years ago

Coverage Status

Coverage remained the same when pulling ddbc1dd7f32a2bb09cd546b6ee5de66c16e40206 on gitlab-grit-gem into e873bb84ac3c4f8249311490d6a7c6ac9127625f on master.

ranmocy commented 11 years ago

I turned to gitlabhq/grit from mojombo/grit since the original one hasn't been updated for a long time. You guys are really hard-working on these.

At the same time, I am using Jekyll which depends on Grit. But gitlabhq/grit change name to gitlab-grit will make Jekyll can not find Grit, though they are doing the same thing.

Also, these commits only change the gemspec filename, but are still using Grit as the module name. This means I can not install two gems gitlab-grit and grit at the same time. That will cause namespace confliction.

So, any suggestion? Maybe you can provide two gemspecs? Then when I add this git repo to my Gemfile, I can specific the gem's name.