First (second) dev.to article! Learn to hit the save button, Jonathan!
You can create aliases both on the repo level and globally just by adding...
For further actions, you may consider blocking this person and/or reporting abuse
That is good stuff, the only issue with this is that if you become dependent on these specific commands and you have to use a different environment (someone else's machine) you could forget the actual commands.
I use text expander on osx to do similar things with common git commands.
Just something to keep in mind. 😁
You could always quickly source your alias config from let's say a gist.
Oh yeah, for sure. I strongly advocate learning the commands before making an alias. But if you switch workspaces as much as I do, I'm creating aliases as much as I'm typing the full command.
typo:
git log --onlineshould begit log --onelineHaha, I mistype that one so much that I define
onlineas an alias foronelinein my gitconfig!Haha! Oops! Thanks for catching that!
Fixed.
I always end up relying on *sh aliases rather than using git's alias. In the end,
gsorgstis still better thangit stto me.Great Stuff !! Thanks.
Thanks for writeup.
It would help if guidelines to undo the global alias set up is given here as well.
One of my favourites is git config --global alias.oops "commit --amend --no-edit"
Interesting that git has this feature.
What is the advantage over just using shell aliases? Does autocompletion work in one case but not the other?