-
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
"gh" git alias clashes with github-cli #1498
Comments
Not sure what we want to do about that... We've had conflicts before (see #825, #867, and #141), similar discussions there. We will not be able to make everyone happy. If you are using both the Bash-it Git aliases and the GitHub CLI, you can still include a Ironically, there has been a similar discussion on GitHub's CLI a while back, from what I remember, back then they switched from a previous version of |
Hmm yes I agree we can't make everyone happy, and unset is a solution for anyone wanting to fix it. |
Greetings, I've seen the related PR but thought to discuss here instead of there ... Would it be useful to :
I think a rule to conditionally-enable aliases is okay when the the alias and the potentially-overridden command are related. We could think of Additionally, its feels like a fair assumption that anyone taking the time to install the new [edit] Elaboration |
@davidpfarrell Sounds good to me, I'll amend the PR. |
Yes, that sounds like a good compromise to me as well. I'll take a look at the PR... |
PR has just been updated. |
GitHub released a new CLI https://cli.github.com/
The command is called
gh
, which clashes with thegh
alias set by the bash-it git plugin.The text was updated successfully, but these errors were encountered: