Cover image for 5 Great Git CLI Shortcuts

5 Great Git CLI Shortcuts

jrgould profile image Jeff Gould ・4 min read

I think we're all onboard with git these days - it's the best way to collaborate on code with a team or to just keep things organized, synchronized, and tidy when you're working alone. But there's still a great divide amongst git users - those who are Git CLI purists, and those of us who are happy to fire up the likes of Tower, SourceTree, Github Desktop, or one of the (probably) hundreds of other options.

CLI users will argue that it's faster and easier to use Git on the CLI but GUI users like myself are usually thinking, "I don't have that much room in my brain, I like buttons..." And, honestly, I think both are right. I've recently been working on my Git CLI skills and a great way to get better at using Git on the CLI is to create aliases for things you do often, especially when they require complex git commands - so here are a few of my favorite git aliases, straight from my .zshrc:


alias gro="git reset --hard @{u}"

In my mind, gro is short for "git reset origin" but I think the whole #{u} thing means upstream tracking branch or something like that. I'll use this when I just want to make sure that I'm working with exactly the same version of this branch that's on github. Now, you can use git pull which will merge remote changes into your local branch or just fast-forward the branch if it can - but I like gro because it will just blow away any edits or even commits that I've made in my current working tree which is often useful if I've been doing some experimenting but now I'm ready to get down to business.


alias gpub="git push --set-upstream origin $(git_current_branch)"

Whenever I'm working on a new branch and am ready to push it up to github I'll just run gpub (shorthand for "git publish") which handles the minutia of telling my origin repo what I want the branch to be called (obviously, I just want it to be the same) and setting up the tracking so that I can just git push my changes in the future. If you try to git push when you don't have a tracking branch, git will give you an error that guides you in the right direction, but gpub is just so much easier.


alias gst="git status -sb"
alias gsb="gst"
alias gss="gst"

This is an easy one, gst is just a better git status because it throws on the -s option which generates less verbose output (easier to read) and the -b option which shows the current branch and tracking branch at the top (eg ## dev...origin/dev). I also have a few aliases for the original alias because sometimes I forget.

"Why not use gs as the alias for that, it's so much easier!" Is what you're probably asking yourself. Well, that's because...


alias gs="git stash"

Another super simple one but I do a fair amount of stashing and stash popping. Bonus tip is that you can still add arguments and subcommands to the end of an alias so you'll often catch me running gs push -m "WIP: converting React to Angular" or just gs pop, gs list, etc.

Honestly, I could probably swap the aliases for gs and gst since I'm sure I use git status more than I use git stash but the hard part would be getting my fingers to update their keymaps.


gcr(){ git checkout -t origin/"${@}" }

Okay, not an alias, but a function that basically works like an alias. Short for "git checkout remote", this will let you check out a remote branch locally and set the tracking up for you as well. I often use this after I've copied the branch name from a PR on github so I can run gcr branch-to-review.

I'm particularly lazy, so there's also a bonus alias here for mac users:

alias gcrc="gcr $(pbpaste)"

This is the same as gcr but it will just use the contents of your clipboard for the branch name.

Git Commit

I've got quite a few more git aliases, but those are pretty standard fare and half of the time I forget to use aliases like gp instead of git pull when the git commands are more obvious to me. I think the great part of having aliases set up for the more complex or esoteric git commands that you use is that you don't have to memorize the command right away in order to be able to use it, just remember the alias and you can also use which to remind yourself what it actually does.

$ which gro
>gro: aliased to git reset --hard @{u}

That's super helpful. Another trick I use is to actually group all of my git aliases in a .gitaliases file and import them into my .zshrc file - then I can also set up an alias to list out all of my git aliases, kind of like a cheat sheet!

# somewhere in .zshrc
if [ -f $HOME/.gitaliases ]; then 
  . $HOME/.gitaliases
  alias gcheat="\cat $HOME/.gitaliases"

Git Merge

Do you have any git aliases or even non-git cli aliases, or functions that you couldn't live with out? Let me know!

Posted on by:

jrgould profile

Jeff Gould


Fullstack developer currently focused on Node, React, and JavaScript in general. WordPress / PHP ExPat. New dad.


markdown guide

A nice one is

alias gdammit='git --amend --no-edit'

For those times you were just too quick on the trigger, and want to add some additional staged files to your last commit.

Feel free to use a different alias, like goops or gredo 🤨


I've been meaning to add one like this - thinking gcrap or gdoh, or maybe just gc!


I use this to set git lg to be a cleaner overview of history:

git config --global alias.lg "log --color --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr)%C(bold blue)<%an>%Creset' --abbrev-commit"

Results in a nice tree view of history showing authors, hashes, titles and the tag/branch names.


That's a good one.
I must say that I never goes beyond the aliases that are by default in zsh and oh_my_zsh.

Here is a quick extract of the aliases available in oh_my_zsh :

ga='git add'
gaa='git add --all'
gap='git apply'
glo='git log --oneline --decorate'
grmv='git remote rename'
groh='git reset origin/$(git_current_branch) --hard'
grrm='git remote remove'
grset='git remote set-url'
grt='cd "$(git rev-parse --show-toplevel || echo .)"'
gru='git reset --'
gupv='git pull --rebase -v'
gwch='git whatchanged -p --abbrev-commit --pretty=medium'
gwip='git add -A; git rm $(git ls-files --deleted) 2> /dev/null; git commit --no-verify --no-gpg-sign -m "--wip-- [skip ci]"'

I wish that the aliases in oh_my_zsh were commented to tell you what they do in plain english. I will often look in there and try to add a new one to my arsenal, but that becomes a bit of a research project since I'm not fluent in git commands and typically need to look things up, at least just to be sure that the commands will do what I suspect.


One of my fav aliases I always set up in git's own aliasing config is:

git ac

For git "all commit". Which is an alias for git add .; git commit -m.

To just add & commit everything in one go.


git add . is 'all commit' only if you have changes on the current path. If you have changes in e.g. sibling dir it won't work as you'd have to go up the path which is ... For a true 'all commit' use git add -A.


I do always run this from project root so I'm ok. But I think I'll switch to your suggestion! :)


I like that - I have gc aliased to git commit so I'll usually do gc -am "commit message" but that does have the the drawback of not adding new files and I forget that 90% of the time and then have to amend the commit which is a whole thing.


Today I came across to this one:

alias gconf='git diff --name-only --diff-filter=U'

To list the conficted files after a merge


I use hub and I alias git=hub

then I have

git sync, git pr list, git pull-request create, git release etc...


Just created this little handy alias for interactive rebase

alias gitrebase='git checkout master && git pull && git checkout - && git rebase -i HEAD~$(git rev-list --count HEAD ^master)'