git config blame.ignoreRevsFile
Arnout Boks (via Cédric Luthi):
A long-standing objection to making bulk changes to code using automated tools (e.g. to conform to a given code style) is that it clutters the output of
git blame. With git 2.23, this does not have to be the case anymore![…]
Because these bulk changes render
git blameuseless, many teams refrain from applying automated style changes of this magnitude. That means they have to live with either a coding standard that they would rather not have, or with a codebase that does not follow their standards.[…]
Using
--ignore-rev, one can specify a commit to be ignored bygit blame.[…]
When multiple bulk commits were added over time, it takes quite some effort to add a
--ignore-revfor each of them in order to get a ‘clean’ output forgit blame. Luckily, git also provides a way to make this easier on us. In your repository, create a file to hold commit hashes of commits to be ignored bygit blame. Naming this file.git-blame-ignore-revsseems to be a common convention.
