3 ms·
> I agree this is terrible primarily because it muddles up any git-blame based workflow for debugging regressions. ...it occurs to me, this feels like you're c
by Wowfunhappy 2y ago
> I agree this is terrible primarily because it muddles up any git-blame based workflow for debugging regressions.
...it occurs to me, this feels like you're conforming to the tool instead of the other way around.
Is there a reason git blame doesn't have an "ignore whitespace" option? Is it harder than it seems?
- nemomarx 2y agoI would think the issue is that if you format someone else's code, gitblame then sees you editing that code? Unless you can mark that commit as white space changes only somehow
- senderista 2y agoYou can tell `git blame` to ignore entire commits: https://gist.github.com/kateinoigakukun/b0bc920e587851bfffa98b9e279175f2 https://gist.github.com/kateinoigakukun/b0bc920e587851bfffa9...
- mattnewton 2y agoIt’s more than white space, autoformatters can change a lot, notable will often change line numbers by introducing or removing breaks