We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I get this wrong all the time, probably the reason is that other CLI adopted "open" to perform similar actions. Example that come to mind:
open
bundle open
gem open
powder open
Of course I know* that I can alias it in my .gitconfig, but maybe it will come useful to others.
.gitconfig
* I just found it works
The text was updated successfully, but these errors were encountered:
I agree it may make sense to rename it to open for the same reason. But maybe this could be done after 2.2.0.
Sorry, something went wrong.
That's not a bad idea. I just hope git core doesn't add a command called open.
hopefully even if they'll do the behavior will be pretty much the same…
Also https://github.com/paulirish/git-open by the good @paulirish is the first result I got after searching for "git open"
No branches or pull requests
I get this wrong all the time, probably the reason is that other CLI adopted "open" to perform similar actions. Example that come to mind:
open
bundle open
gem open
powder open
Of course I know* that I can alias it in my
.gitconfig
, but maybe it will come useful to others.* I just found it works
The text was updated successfully, but these errors were encountered: