News for hackers. Stuff that matters.
Re:Manage GitHub Issues with the command line by niggler on Sunday April 21, 2013 @09:48AM (#5584808)
When GitHub is down, the thing I actually miss is the issues. You can't seem to clone them. Are there any public issue trackers that can be easily replicated?
Re:Manage GitHub Issues with the command line by drhayes9 on Sunday April 21, 2013 @10:22AM (#5584918)
Have you seen ticgit? https://github.com/jeffWelling/ticgit

All the tickets are kept in a branch within your git repository. It offers a Gem-based CLI, "ti".

It wasn't quite as frictionless as I like my issue trackers to be (especially for personal projects), but it does what it says on the box.

Re:Manage GitHub Issues with the command line by joelcox on Sunday April 21, 2013 @01:39PM (#5585587)
I've been using `ghi` for quite some time now and I'm definitely a fan. One feature I'd love to see is offline-mode because I often work on some personal projects during my commute.
Re:Manage GitHub Issues with the command line by XorNot on Sunday April 21, 2013 @05:54AM (#5584437)
This would go great with Hub (http://defunkt.io/hub/) which provides pull-request integration.
Re:Manage GitHub Issues with the command line by amichal on Sunday April 21, 2013 @07:48AM (#5584578)
so does ghi.
Re:Manage GitHub Issues with the command line by orta on Sunday April 21, 2013 @08:22AM (#5584631)
I have a similar gem but for pivotal tracker: https://github.com/raul/pt
Re:Manage GitHub Issues with the command line by jamesbritt on Sunday April 21, 2013 @01:31PM (#5585541)
I suspect this is something everyone feels compelled to do.

For github I wrote ghissues: https://github.com/Neurogami/ghissues

But ended up not using it (forget why) so it's likely way out of date.

For Pivotal I wrote Pivotal Slacker; that was in 2009; Github ended up hosing the repo somehow, and soon after I stopped using PT.

Anyways, both of these grow out that little voice that says, "I wish I could do this stuff at the command line. How hard could it be? I'll just write some code ... "

Re:Manage GitHub Issues with the command line by yummyfajitas on Sunday April 21, 2013 @08:44AM (#5584672)
I also have one for github and redmine.

https://github.com/stucchio/idli

Seems like a lot of people want a tool like this.

Re:Manage GitHub Issues with the command line by chimeracoder on Sunday April 21, 2013 @12:28PM (#5585318)
Unfortunately, this only seems to work on the remote named 'origin'. If your branch corresponding to GitHub is named something else (ie, 'github'), it won't work.

Nice work otherwise, though - I've been thinking about writing something like this for my own purposes in Go for a while now; glad to see someone else had the same problem.

If I have some time later today, I'll put in a pull request... unless someone beats me to the punch.

Re:Manage GitHub Issues with the command line by stephencelis on Sunday April 21, 2013 @01:51PM (#5585630)
It actually lets you do this already, though the documentation is relegated to a manpage that doesn't get installed automatically. It checks, in order, for:

  - $GHI_REPO env var
  - git config ghi.repo
  - remote named "upstream"
  - remote named "origin"
So you can just use "git config ghi.repo username/reponame" to get the behavior you want.