-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move from gh to hub, the new official GitHub CLI #392
Comments
The completion file is basically the same for gh and hub, the command name has changed and some minor changes, I think. Now hub is in a release candidate state, so we can do the update when finally released. Additionally, we can add an alias to maintain compatibility ( |
Another option is to have separate plugins+completion, one for gh, and other for hub. |
Wouldn't it be easier to detect whether the
Same for the completion. If there's a chance that you want to have both If the differences are significant, I agree that it would be better to have two different plugin/completion files. If it's just the name of the command, it should be possible to detect which one is installed and then alias that. |
👍 for detecting where we can. FWIW, I use |
Done in PR #562 |
The project gh has been adopted as the new official GitHub CLI (hub).
See this: mislav/hub#475
So it is necessary to update:
plugins/available/gh.plugin.bash
completion/available/gh.completion.bash
The text was updated successfully, but these errors were encountered: