[color]
custom.rev = red
custom.bm = yellow
custom.date = green
custom.author = blue
[alias]
lg = log -G --template "{label('custom.rev',node|short)} - {if(bookmarks,'(')}{label('custom.bm',bookmarks)}{if(bookmarks,') ')}{desc|firstline} ({label('custom.date',date|age)}) <{label('custom.author',author|person)}>" -b .Better to learn how to do meaningful queries against the tree (is branch X in branch Y, what's the merge base of X, Y, Z, etc.) and let the computer understand it for you.
And usually what I want to see when I do git log these days is either --first-only on master or master.. on a topic branch.
I actually thought that this was originally going to be an overview of tig[0] which has completely replaced git log for me.
Rather, I use tig to get a quick glance at commit history and staged / unstaged changes.
Can someone explain the relative upsides and downsides to using tig vs git lg?
With that transparent terminal? No. There's a massive distraction behind it.
[F2] g l l
This is what my .gitconfig looks like right now: https://github.com/bilalq/dotfiles/blob/master/git/gitconfig
I hardly ever use git log anymore since SourceTree lets me know very easily who commited when, when and from what branch. What's not to love?
wat?
has had these for a long time. both git lg and git gl