Great work, but when I run gh help remote
, I get the man page for git remote
. The user expects to see a page about the features that gh
adds to git remote
(namely origin and -p). hub
does this too, but I guess that it is supposed to be used as an alias for git
, so when you run git help remote
, you want to see almost always information for git remote
, not hub remote
. gh
isn't yet supposed to be used as an alias for git
, so I can't see why it should provide help for git
.
In other words, when I run git help remote
, I want to view help for git remote
. When I run hub help remote
, I probably have git
aliased as hub
, so I want to view help for git remote
. But when I run gh help remote
, I don't have aliased git
as gh
, so I want to view help for gh remote
.
I don't know: if you have plans to copy hub
and support aliasing to git
, then I see why you would keep the current help structure. On the other hand, if you don't have plans to copy hub
, IMHO you should change gh help
to provide help for gh
.
The reason I mention hub
is that you state that hub
is a reference implementation to gh
, so I see where you're coming from.
PS: The above rant is only about non-GitHub-specific commands (commands that are not specific to GitHub - gh remote
for example - but are extended by gh
). GitHub-specific commands are done right.