Blog: optimizedbyotto.com
You need bisect only as a last resort. Effective use of git blame
, git log -p -S <keyword>
etc has always been enough for me. Also, the projects I work with take 10+ minutes to compile even when cached, so doing tens of builds to bisect is much slower than just hunting for strings in git commits and code.
I had the same feeling until I started using gitk
. I always have a gitk
window open and press F5 to reload, so it shows me the state of everything after I’ve run git commands. Now I grasp everything much better.
We just need specific portals for sharing that remember your homeserver. See for example https://mastodonshare.com/.
I just prefix all my git aliases with
g-
. So for status I typeg-s<tab>
.