Oh wow, its like git commands for my ...terminal?<p>All jokes aside, this is actually really helpful, but as someone who uses the terminal on a daily basis, I have the commands for Git like baked into memory (or at least the ones I use on a regular basis), and wouldn't be interested in trying to change my work flow (a lot of my stuff is scripted). However, for someone learning git using github, something like this could be extremely helpful!
Additionally, there's hub [0], by a developer at GitHub. It can have 'git' aliased to it, and then pass through the git commands it doesn't handle.<p>0: <a href="http://defunkt.io/hub/" rel="nofollow">http://defunkt.io/hub/</a>
I usually just view the website for GitHub specifics. Can anyone who uses a GitHub CLI application in their workflow explain how this compares to "hub" and the other applications? The only "extension" to git I've gotten comfortable with is Git Flow since that just makes what I would already do easier. Is there really some big improvement to be had by incorporating a tool like this into my workflow?
Looks quite nice. But it definitely needs improvement.<p>I think it would be much better to specify a repo using user/repo syntax instead of "-u user -r repo". Also if I'm in a git repository it should use the origin repo and NOT myusername/currentdirectory.<p>For now a combination of hub & ghi works better for me.
it's not entirely clear what the value of --submit represents. i know that it's required and it's an account name on gh. i suspect it's the account of the target repo? if so perhaps it should not be required and should default to the origin, no?