On: Black, the uncompromising Python code formatter, i...

[rr808]

Anyone have a foolproof way to reformatting all the code in a repo without screwing up history? I've seen some complicated commands which seem too sketchy to a git novice like myself.

[mumblemumble → rr808]

Do it all in one commit.

Then put that commit's (full) sha in a file named something like .git-blame-ignore-revs

Then `$ git config blame.ignoreRevsFile .git-blame-ignore-revs`

[rr808 → mumblemumble]

Thanks, that is helpful, esp I can google that to get more docs. One issue is everyone in the team needs to do so, but its probably worth it.