defunkt / github-gem
- Source
- Commits
- Network (66)
- Issues (11)
- Graphs
-
Branch:
master
-
github forkwants to create a fork and then clone it. Typically, I clone someone else's repo to check it out, then decide later to fork it. It would rock ifgithub forkwith no arguments from within a repo would fork the cloned repo and set up my fork as the neworigin.Comments
-
The issue email that is sent out when an issue is added to a repository that you're watching has the "Read more..." link as this (example from #1 of this repo): http://github.com//defunkt/github-gem/issues/1/find whereas it should be: http://github.com/defunkt/github-gem/issues/#issues/1
Comments
-
$ github /var/lib/gems/1.9.0/gems/defunkt-github-0.3.4/lib/github/extensions.rb:11: warning: undefining `object_id' may cause serious problem /var/lib/gems/1.9.0/gems/defunkt-github-0.3.4/lib/github.rb:149:in `module_eval': /var/lib/gems/1.9.0/gems/defunkt-github-0.3.4/lib/commands/commands.rb:40: syntax error, unexpected ')' (SyntaxError) helper.tracking.sort { |(a,),(b,)| a == helper.origin ? -... ^ /var/lib/gems/1.9.0/gems/defunkt-github-0.3.4/lib/commands/commands.rb:40: syntax error, unexpected '|', expecting '=' ...per.tracking.sort { |(a,),(b,)| a == helper.origin ? -1 : b ... ... ^ /var/lib/gems/1.9.0/gems/defunkt-github-0.3.4/lib/commands/commands.rb:40: syntax error, unexpected '}', expecting keyword_end ...rigin ? 1 : a.to_s <=> b.to_s }.each do |(name,user_or_url)| ... ^ from /var/lib/gems/1.9.0/gems/defunkt-github-0.3.4/lib/github.rb:149:in `load' from /var/lib/gems/1.9.0/gems/defunkt-github-0.3.4/lib/github.rb:66:in `block in activate' from /var/lib/gems/1.9.0/gems/defunkt-github-0.3.4/lib/github.rb:65:in `each' from /var/lib/gems/1.9.0/gems/defunkt-github-0.3.4/lib/github.rb:65:in `activate' from /var/lib/gems/1.9.0/gems/defunkt-github-0.3.4/bin/github:8:in `' from /var/lib/gems/1.9.0/bin/github:19:in `load' from /var/lib/gems/1.9.0/bin/github:19:in `'Comments
I'd really like to see this fixed soon... Arch has moved to ruby 1.9, which means that this app no longer works without installing 1.8 alongside, which is rather ugly.
I've made fixes in my fork which work for me. Whether or not they maintain complete 1.8.6 and 1.8.7 compatibility, I'm not sure.
Would those be the 5 commits from your 1.9.x branch? Probably for packaging purposes I'll format-patch those commits and apply them onto the main branch for now.
Yes. And I've confirmed the test-suite runs 100% on 1.8.7.
Here's an update on Ruby 1.9 status with the github 0.4.0 gem: simply running the
githubcommand fails withruby 1.9.1p243 (2009-07-16 revision 24175) [i686-linux].% github /usr/lib/ruby/gems/1.9.1/gems/github-0.4.0/lib/github/extensions.rb:11: warning: undefining `object_id' may cause serious problem /usr/lib/ruby/gems/1.9.1/gems/github-0.4.0/lib/github.rb:151:in `module_eval': /usr/lib/ruby/gems/1.9.1/gems/github-0.4.0/lib/commands/helpers.rb:5: syntax error, unexpected ':', expecting keyword_then or ',' or ';' or '\n' (SyntaxError) when %r|^git://github\.com/([^/]+/[^/]+)$|: $1.split('/') ^ /usr/lib/ruby/gems/1.9.1/gems/github-0.4.0/lib/commands/helpers.rb:6: syntax error, unexpected keyword_when, expecting keyword_end when %r|^(?:ssh://)?(?:git@)?gith... ^ /usr/lib/ruby/gems/1.9.1/gems/github-0.4.0/lib/commands/helpers.rb:6: syntax error, unexpected ':', expecting keyword_end ...@)?github\.com:([^/]+/[^/]+)$|: $1.split('/') ... ^ /usr/lib/ruby/gems/1.9.1/gems/github-0.4.0/lib/commands/helpers.rb:8: syntax error, unexpected keyword_end, expecting $end from /usr/lib/ruby/gems/1.9.1/gems/github-0.4.0/lib/github.rb:151:in `load' from /usr/lib/ruby/gems/1.9.1/gems/github-0.4.0/lib/github.rb:68:in `block in activate' from /usr/lib/ruby/gems/1.9.1/gems/github-0.4.0/lib/github.rb:67:in `each' from /usr/lib/ruby/gems/1.9.1/gems/github-0.4.0/lib/github.rb:67:in `activate' from /usr/lib/ruby/gems/1.9.1/gems/github-0.4.0/bin/github:8:in `<top (required)>' from /usr/bin/github:19:in `load' from /usr/bin/github:19:in `<main>'This is a known issue which I've fixed in my branch. It's because ruby1.9 no longer supports the
when cond: blahsyntax. You need to use newlines orwhen cond then blah.Thanks for the update. I will use your fork for now and I hope your changes are pulled into upstream soon. :-)
-
github network list fails with "redirection forbidden" on private repo
6 comments Created 6 months ago by kocoloskTraceback looks like
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/open-uri.rb:174:in `open_loop': redirection forbidden: http://github.com/user/repo/network/members.json -> https://github.com/user/repo/network/members.json (RuntimeError)
from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/open-uri.rb:132:in `open_uri' from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/open-uri.rb:518:in `open' from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/open-uri.rb:30:in `open' from /Library/Ruby/Gems/1.8/gems/defunkt-github-0.3.4/lib/commands/helpers.rb:340:in `get_network_members' from /Library/Ruby/Gems/1.8/gems/defunkt-github-0.3.4/lib/commands/network.rb:23:in `command' from /Library/Ruby/Gems/1.8/gems/defunkt-github-0.3.4/bin/../lib/github/command.rb:25:in `send' from /Library/Ruby/Gems/1.8/gems/defunkt-github-0.3.4/bin/../lib/github/command.rb:25:in `call' from /Library/Ruby/Gems/1.8/gems/defunkt-github-0.3.4/bin/../lib/github.rb:74:in `invoke' from /Library/Ruby/Gems/1.8/gems/defunkt-github-0.3.4/bin/../lib/github.rb:68:in `activate' from /Library/Ruby/Gems/1.8/gems/defunkt-github-0.3.4/bin/github:8 from /usr/bin/github:19:in `load' from /usr/bin/github:19I didn't actually have an "origin" branch in this repo at first, so I added one that looks like
git remote show origin
* remote origin URL: git@github.com:user/repo.git HEAD branch: master ...Comments
same problem here. Tried modifying the URLs used to go straight to the https links, but then other things break...
Yep this newer fix works. Much appreciated.
It's also a little nicer with a -s to curl to to remove the progress display.
-
Comments
Never fails, once I push I notice something wrong. New commit
-
using it on an already cloned repository fails
0 comments Created 2 months ago by digi604$ github network Error: remote 'origin' is not a github URL
origin url is:
Fetch URL: git+ssh://git@github.com/digi604/django-cms-2.0.git
Push URL: git+ssh://git@github.com/digi604/django-cms-2.0.gitComments
-
Update on "Fetching and Evaluating Downstream Changes" documentation
0 comments Created about 1 month ago by peterbeIt says to do
gh fetch ...andgh merge ...but those are no longer available commands.I suspect you have lumped them under the
gh pull ...command instead. I would do a fork + pull but I'm a bit uncertain I've fully understood this stuff as I'm brand newbie to it.Comments
-
network commits has formatting issues if commit message has :: in it
0 comments Created about 1 month ago by wfarrwfarr@lawn-143-215-98-135:~/Code/github-gem$ bin/github network commits gathering heads ========================================================================================= These are all the commits that other people have pushed that you have not applied or ignored yet (see 'github ignore'). Some things you might want to do: * You can run 'github fetch user/branch' (sans '~N') to pull into a local branch for testing * You can run 'github cherry-pick [SHA]' to apply a single patch * You can run 'github merge user/branch' to merge a commit and all the '~N' variants. * You can ignore all commits from a branch with 'github ignore ..user/branch' ========================================================================================= using cached... c325c9 (tekkub/master) tekkub@gmail.com Bugger, how did that get in there 2 weeks ago 52a098 (tekkub/master~1) tekkub@gmail.com Add upload command 2 weeks ago ce9544 (vertis/master) vertis@coreguardian. removed curl and replaced with net http cbc00b (msadouni/master) matthieusadouni@gmai Fix 'operation not supported git che E045)' on OSX 474067 (jgdavey/master) josh@joshuadavey.com Adding specs and fixing typo (bug) f 2 days ago c628a8 (nex3/master) nex342@gmail.com Be noisy when GitHub Command#sh hasAs you can see in the case of nex3, msadouni, and vertis's commit messages, when the commit message contains '::', it breaks the parsing and doesn't show the date in the appropriate spot.
Comments
-
This applies to v0.4.0.
Although the command seems to work, the key ingredient (the curl command to actually create the repo on github) has a typo.
I've forked and fixed this, adding a slight bit more verbose output as well, following the pattern that Dr. Nic started in his recent enhancements.
Comments
-
It seems that the GitHub gem needs the json gem to work properly, as I had some issues when I installed it yesterday:
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems /custom_require.rb:31:in `gem_original_require': no such file to load -- json (LoadError) from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `require' from /Library/Ruby/Gems/1.8/gems/github-0.4.0/bin/../lib/github.rb:9 from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `require' from /Library/Ruby/Gems/1.8/gems/github-0.4.0/bin/github:6 from /usr/bin/github:19:in `load' from /usr/bin/github:19Comments
-
github gem requires json gem, but doesn't depend on it
0 comments Created 28 days ago by indirectThe github gem should depend on the json gem, so that
gem install githubwill install it.I installed the github gem, but when I ran
gh, I got this:/Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in `gem_original_require': no such file to load -- json (LoadError) from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in `require' from /usr/local/Cellar/Gems/1.8/gems/github-0.4.0/bin/../lib/github.rb:9 from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in `gem_original_require' from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in `require' from /usr/local/Cellar/Gems/1.8/gems/github-0.4.0/bin/gh:6 from /usr/local/bin/gh:19:in `load' from /usr/local/bin/gh:19Comments
-
I've never been able to get the 'gh create' calls to work. I tried all sorts of combinations and trying to specify the repo in different ways. Nada. So I decided to write up an issue...then I decided I'd better just look at the source. And there is, some mysterious github token! I didn't have one. So I googled and discovered that I do have one and I need to set that in my global git config.
Could you please add a line saying that you need to do this step to the install?! Unless I'm missing something how would any normal person know to do this?
Cheers,
KarlPS A check that the token isn't empty would be good in the 'create' calls..or wherever it's needed. Perhaps that would even be enough.
'You haven't configured your GitHub API key! Please go to http://github.com/[github_user] and blah...'Comments





I take it back; this is done already in master, just not released in the gem. Awesome. :)