3 ms·
Maybe just as important: make sure the changes in a commit are related. `git blame` is a criminally underused feature, possibly because the benefits only become
by Vinnl 6y ago
Maybe just as important: make sure the changes in a commit are related. `git blame` is a criminally underused feature, possibly because the benefits only become clear after you've had the discipline of paying attention to what goes in a commit. However, being able to pull up the context of related code right from the context of the line you're looking at [1] (from my post at [2]) can be very valuable.
[1] https://vincenttunru.com/img/Commits-are-documentation/annotations.png https://vincenttunru.com/img/Commits-are-documentation/annot...
[2] https://vincenttunru.com/Spend-effort-on-your-Git-commits/ https://vincenttunru.com/Spend-effort-on-your-Git-commits/
- ericol 6y agoI'm totally, utterly in love with Github's "Show blame previous to this commit" feature.
- graton 6y agoMany text editors now have this feature built in. Myself I use vim and the vim-fugitive plugin. Being able to do ":Gblame" is amazing. And then being able to step back in time to see what the code looked like before this commit is great too.