Introduction
I've been requested multiple times about sharing my .gitconfig
to copy my aliases.
I use git aliases for two reasons:
- To improve productivity.
- 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
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'
git help status
There are two aliases I find interesting for beginners:
git tuto
git tuto2
Comments and suggestions with different approaches are always welcomed.
Latest comments (48)
I dont use any :))
xD
general ones:
And some specific commit messages (conventional commit is a thing):
Thanks for sharing @vikmstr !!!
using zsh
Really like this discussion. Added many of these to my .gitconfig
Thanks @hasii2011
Wow, I think @tpenguinltg probably has some of the most elaborate ones I've seen, nice config you have there!
And all of you have shared practical examples; hats off to the author and others who shared their aliases. I will add mine here, though most of them are a bit generic and unimaginative. 😅
Thanks for sharing @killshot13 !!
I didn't read all that were postet but here are mine that I love the most.
Most used by me is glogl (git log last) and glog -100 (git log last 100)
It creates an output like:
Thanks @loebkes for sharing. Really cool one.
I really only do two
git fixup
And
My first git alias
Jamund Ferguson ・ Apr 16 '21 ・ 2 min read
Thank you @jessekphillips
Wow! didn't know that. Thanks @natescode !!
NB "git wip" conflicts with standard alias setting for Gerrit, for which injection of an alias series "ready", "wip", etc. is suggested (and supported by a local installer).
The thing that confuses is that alias set is very uneven in sense of pressings. If you press something on keyboard, you anyway press some sequences, and all git commands start with "git " - already 4 presses... After it, difference, for example, between "git br" = "git branch -r" and "git b -r" where "b" is already aliased as "branch" is nearly void, compared with any other difference. This suggests the alias set is accrued historically without substantial reconcerning.
Alias "db" is dangerous. I prefer to write such actions only explicitly. Same for "op": it's normal to refer to something done a few days ago, and for "vc". (BTW do you use IDE? Something like "git clean -dfx -e .vscode" would be better.)
What is use case for "search"?
"last" could be extended with "--stat" to show changes, because anyway only a single commit is printed.
OTOH, it clearly exposes some manners and developing approaches - as presence of "main" and "devel" branches. For me, it showed some features I was unaware or forgot them due to standing out of usual habits... thanks for this.
Formatting was broken - e.g. what is "git alias" is unparseable (seems the website markdown was active). If it allows editing the post, please reconsider.
To compare, my typical set (with comments):
Maybe more specific to my manner, but it is typical to cache only some changes among ones in file (others could be for later commits, not committed as debug, etc.) - just interactive mode is not enough. Git's recalculating of chunk line count works well enough.
In rebase, sometimes it is needed to see full patch to apply now.
Just shortening for all branch related commands.
"current branch" in an easy solitary way.
To adjust the last commit with catch-up changes.
Habitual from previous VCSes. To edit commit message is more useful because it never should be one-liner in a final version.
Obviously needed before commit is created from parts.
Maybe "cp -n", etc. is enough but often used in some flows.
Convenience for log view styles.
For some flows, merge is impossible - it's required to actualize the working state regularly.
Interactive rebase helpers in different styles to keep propositions clear.
Rare but... for a new work, having basic empty commit is crucial to keep the first commit clear. Otherwise, complex dances with filtering are needed. (I'm wondering why it is not in Git base logic.)
I'd also note some crucial settings out of aliases:
To show base version for a conflict - crucial both for a human and automatic merging tools.
Otherwise some tools avoid paging.
Never push many-to-many without an explicit specification in a command.
Useful default to minimize underwater pull effects.
Thanks @netch80 I have reviewed the post and I some backslashes were missing. Thanks for your comments. Really helpful.
Also, for work specifically, my company works on GitHub, and I have a bash script to easily create a new PR from the current branch.
I name it
git-new-pr
, and add it to my$PATH
. Then, I can callgit new-pr
, and it'll automatically open up a page for a new PR in my browser.This script is for macOS. So, the last line opens the URL in the default browser. If using Linux, this could be
xdg-open $PR_URL
. Also, a specific browser could be specified.Most people would just use the GitHub cli for this, but I've never bothered installing it, and this works really well.
Thanks for sharing @goodevilgenius !!
I have only two aliases:
Haha! Love the second one. Thanks for sharing @primo
Nice ones also @ginomempin . Thanks for sharing!
Great aliases you've got!
I have just one git alias at the moment and that is:
This comes very handy especially if you contribute to open source projects frequently.
Thanks @thisisobate ! Added to my list
Sorry to be a Party Pooper!!
But why not use ZSH with the Oh ZSH add-on and it's various plugins. ohmyz.sh/
Even posted on Dev.to
dev.to/0xkoji/do-you-know-oh-my-zs...
Great list! Will definitely add a few of these.
A few more that I like:
Thanks for sharing @ehaynes99 ! I will take note of yours too.