Hi everyone
Today I am writing about gh
, the Github wrapper that entered beta. Also the Github devs are looking for feedback on thier new cli tool.
So after installing it, I first tested if it enters in conflict(fights) with hub
, that I already had it installed.
hub --version ✔ at 17:31:38
git version 2.20.1
hub version 2.7.0
gh --version ✔ at 17:31:49
gh version 0.5.7 (2020-02-20)
https://github.com/cli/cli/releases/tag/v0.5.7
A new release of gh is available: 0.5.7 → v0.6.1
https://github.com/cli/cli/releases/tag/v0.6.1
No problems so far.
So As you can see Dear reader they don't enter conflicts or collide.
Going a bit further I wanted to test gh
in a project created with hub
to see if it can manage this challenge.
If you followed my articles Dear reader, you may have read about my Absinthe series, so let's test if gh
can use the following command as hub
.
hub checkout -b 01-new_branch
But when I tried gh
the result was:
gh pr checkout -b 01-new_branch ✔ at 17:37:23
unknown shorthand flag: 'b' in -b
Usage:
gh pr checkout {<number> | <url> | <branch>} [flags]
Global Flags:
--help Show help for command
-R, --repo OWNER/REPO Select another repository using the OWNER/REPO format
So no -b
flag for creating a new branch from an existing one?!
Then when I executed gh
for the first time it wanted for me to log in to my GitHub using the browser and not the terminal.
I think that I will report these things to GitHub regarding gh
and ask them nicely to keep the normal git commands
so that we don't need to learn a new git
!?
What do you think Dear Reader? Have you tried gh
yet?
If you enjoyed this article and also found it useful, share it on social.
Top comments (0)