We've been migrating to prettier, & (alas) switching from tabs to spaces across our many microservice projects.
The one saving grace is that git 2.23 (august 2019) added an --ignore-rev and --ignore-rev-file in to git blame[1]. There's no standard file, unlike .gitignore, alas, so we have .gitignorerev as our own personal standard in our migration guide.
This isn't perfect. Github for example doesn't know anything about this. We have a lot of vscode users but I don't think anyone in that world has gone & figured it out. I wish there were a standard file, a lot. But it's still a huge help, a good start.
"At a previous company, there was an “infamous” commit in our main repository. The commit was about 10 years old, and it replaced every tab with 4 spaces."
The one saving grace is that git 2.23 (august 2019) added an --ignore-rev and --ignore-rev-file in to git blame[1]. There's no standard file, unlike .gitignore, alas, so we have .gitignorerev as our own personal standard in our migration guide.
This isn't perfect. Github for example doesn't know anything about this. We have a lot of vscode users but I don't think anyone in that world has gone & figured it out. I wish there were a standard file, a lot. But it's still a huge help, a good start.
[1] https://git-scm.com/docs/git-blame/2.31.0#Documentation/git-...