DEV Community

Cover image for What are your git aliases?
Jose Angel Munoz
Jose Angel Munoz

Posted on • Edited on

What are your git aliases?

#git #beginners #tutorial #productivity

Introduction

I've been requested multiple times about sharing my .gitconfig to copy my aliases.

I use git aliases for two reasons:

  1. To improve productivity.
  2. To remember interesting git commands and learn from them.

My Gitconfig

These are my aliases included in my ~/.gitconfig file for your reference:

[alias]
    a = add .
    aliases = config --get-regexp alias
    alias = ! git config --get-regexp ^alias\\. | sed -e s/^alias.// -e s/\\ /\\ $(printf \"\\043\")--\\>\\ / | column -t -s $(printf \"\\043\") | sort -k 1
    ap = add . -p
    addups = remote add upstream
    bd = branch -d
    bi = bisect
    bl = branch -l
    blr = branch -a
    br = branch -r
    ca = commit -a
    cam = commit -a -m
    ci = commit -m
    cia = commit --author='imjoseangel <anotheremail@example.com>' -m
    cm = commit
    co = checkout
    colast = checkout -
    comments = commit -m 📒Comments
    count = rev-list --count devel
    db = branch -D
    forgetAbout = rm --cached
    formatting = commit -m 💅Formatting
    fp = fetch -p
    grep = grep -F
    laf = fsck --lost-found
    last = log -1 HEAD
    latest = log -5 --pretty --oneline
    ls = ls-files --others --exclude-standard -z
    mend = commit --amend
    nb = checkout -b
    op = gc --prune=now --aggressive
    pdo = push -d origin
    pf = push --force-with-lease
    po = push origin
    pou = push --set-upstream origin
    pr = pull --rebase
    pror = remote prune origin
    prud = pull --rebase upstream devel
    prum = pull --rebase upstream main
    prune = remote update --prune
    ptag = push origin --tags
    ra = rebase --abort
    rc = rebase --continue
    refactor = commit -m 👷Refactor
    remotes = remote -v
    renb = branch -m
    rh = reset --hard
    rhh = reset --hard HEAD
    ri = rebase -i upstream/devel
    rim = rebase -i upstream/main
    rl = reflog
    rp = repack -ad
    s = status -s
    search = rev-list --all
    sh = show
    short = shortlog -sn
    sign = commit --amend --no-edit --signoff
    st = status
    stashes = stash list
    tests = commit --allow empty -m ✅Tests
    tuto = help tutorial
    tuto2 = help tutorial-2
    unstash = stash pop
    vc = clean -dfx
    wow = log --all --graph --decorate --oneline --simplify-by-decoration
Enter fullscreen mode Exit fullscreen mode

Running git alias after adding to the .gitconfig shows the list of all the aliases as a reference list.

To get more info, just run git help <command or alias>. For instance:

git help st
'st' is aliased to 'status'
Enter fullscreen mode Exit fullscreen mode 
git help status
Enter fullscreen mode Exit fullscreen mode

There are two aliases I find interesting for beginners:

git tuto
git tuto2
Enter fullscreen mode Exit fullscreen mode

Comments and suggestions with different approaches are always welcomed.

Oldest comments (48)

Collapse
 
tw2113 profile image
Michael Beckwith •

I mostly just stick with these:

alias gdiff="git difftool"
alias gap="git add -p"

Everything else is longform because I prefer to be familiar with the most common commands in case i'm ever not on a computer that's mine.

Collapse
 
imjoseangel profile image
Jose Angel Munoz •

Thanks @tw2113 I will add them to my list.

Collapse
 
austincunningham profile image
Austin Cunningham •

dev.to/austincunningham/git-log-pr...

Collapse
 
imjoseangel profile image
Jose Angel Munoz •

Nice one @austincunningham Thanks!

Collapse
 
thomasbnt profile image
Thomas Bnt •

Good timing this post!

I recreated my WSL space on my Windows 10, and I created some aliases for git and others commands.

aliases ga="git add"
aliases gc="git commit -m $1"
aliases gp="git push"
aliases gpu="git pull"
Enter fullscreen mode Exit fullscreen mode

😄🙌

Collapse
 
imjoseangel profile image
Jose Angel Munoz •

Good ones @thomasbnt Thank you!!!

Collapse
 
juanfrank77 profile image
Juan F Gonzalez •

Well, my git alias list is not that long. It's like 8 lines which are for the most used git commands. And I don't have aliases for commands with different flags.
But that's the good thing about it, personalization rules.

Collapse
 
motuncoded profile image
Adijat Motunrayo Adeneye •

Hello, how do I add my alias

Collapse
 
imjoseangel profile image
Jose Angel Munoz •

Hi @motuncoded , just create a .gitalias file in your home:

cat ~/.gitconfig, and add your list in the [alias] section as shown in the post.

Let me know if it help.

Thank you!

Collapse
 
fjones profile image
FJones • • Edited

The only one I sometimes configure is git s for status, but even that I usually just type out. One thing I did alias was merging current branch to our integration branch, which lets me easily chain either the push or the push and checkout $currb after it, or waiting for the CI pipeline to start before pushing.

Though I do sometimes think about aliasing m to merge --no-edit and ca to merge --amend --no-edit, because I often forget to add the no-edit param and get annoyed by the need to quit nano.

Collapse
 
imjoseangel profile image
Jose Angel Munoz •

Thanks for your comments @fjones

Collapse
 
necrophcodr profile image
necrophcodr •

I don't believe using aliases is a good idea. I seldom use it even in my shell, but I prefer to leave it out entirely with applications that I might not be the only one using. And Git is definitely not something of which I'm the sole user, so avoiding aliases makes it much easier to remember the full commands as they would be available for my friends and colleagues if I need to help them out, or if I'll be writing documentation on how we're doing certain processes.

In those cases I think using an alias will cause more harm than good, and so I avoid them. The extra keystrokes are not an issue for me, as I'm a slow thinker anyways, haha.

Collapse
 
imjoseangel profile image
Jose Angel Munoz •

I understand @necrophcodr , You can always have them to learn new commands and git options. Thanks for sharing!

Collapse
 
olsard profile image
olsard •

Nice, thanks for sharing.
I would add some of my aliases

no-edit = commit --amend --no-edit
back = reset --soft HEAD~1
back2 = reset --soft HEAD~2
back3 = reset --soft HEAD~3
Enter fullscreen mode Exit fullscreen mode
Collapse
 
imjoseangel profile image
Jose Angel Munoz •

Thanks for sharing you too!!

Collapse
 
tpenguinltg profile image
tPenguinLTG •

My aliases are either things I use regularly or things that I find useful on occasion and would otherwise have to look up every time. I've added explanatory comments to some of the less-obvious aliases.

[alias]
    # File changes
    ## gen-ignore <lang>: Outputs a .gitignore file for `lang` from gitignore.io to stdout.
    gen-ignore = "!_gi() { curl -L -s https://www.gitignore.io/api/$@ ;}; _gi"
    ## ignore/hard-ignore: See https://stackoverflow.com/a/13631525
    ignore = update-index --assume-unchanged
    unignore = update-index --no-assume-unchanged
    hard-ignore = update-index --skip-worktree
    hard-unignore = update-index --no-skip-worktree
    ## ls-ignored: Lists files marked with assume-unchanged.
    ls-ignored = !git ls-files -v | grep '^[[:lower:]]' | cut -c 3-
    ## ls-hard-ignored: Lists files marked with skip-worktree.
    ls-hard-ignored = !git ls-files -v | grep -i '^S' | cut -c 3-
    word-diff = diff --word-diff
    char-diff = diff --word-diff --word-diff-regex='([^[:alnum:]]|[^[:space:]])'
    ## drop [stash_args...]: Like `reset HEAD`, but changes are recoverable from the stash reflog. Forwards arguments to `stash push`.
    drop = "!_drop() { git stash push \"$@\" && git stash drop; }; _drop"
    stat = status --short --branch

    # Commits
    ## init-commit: Initializes the repo and creates an empty initial commit.
    init-commit = !git init && git commit --allow-empty -m \"Initial commit\" -m \"This commit intentionally left blank.\"
    amend = commit --amend --no-edit
    fixup = commit --fixup
    squash = commit --squash

    # Log
    graph = log --graph --oneline
    log-yesterday = log --since=yesterday.midnight --oneline

    # Branches
    pulre = pull --rebase
    ## push-new: Pushes the current branch to `origin` with the same name and sets up tracking.
    push-new = push -u origin HEAD
    push-lease = push --force-with-lease
    ## sq [base_branch]: Starts an interactive rebase from the base of the branch relative to `base_branch`
    ##                   (defaults to `master`; can be any ref) without applying changes on top of `base_branch`.
    sq = "!_sq() { git rebase --interactive --autosquash $(git merge-base HEAD ${1:-master}); }; _sq"
Enter fullscreen mode Exit fullscreen mode

push-new can easily be rewritten to accept other remote names as arguments, and sq's default can be changed to use main or pull init.defaultBranch from the Git config instead of master.

I tend not to use too many short forms or have too many aliases because tab completion exists and I don't want to develop non-portable muscle memory.

Collapse
 
imjoseangel profile image
Jose Angel Munoz •

Wow! I will take some from you and adding to my list of learning commands. Thanks!

Collapse
 
michi profile image
Michael Z •

I have a handful of useful git aliases that help me be more productive:

Collapse
 
imjoseangel profile image
Jose Angel Munoz •

Thanks for sharing @michi

View full discussion (48 comments)