12 ms·
When I switched the company to Black, I reformatted the whole repository history with it. Every developer had to clone the repository again and reapply their lo
by skrause 5y ago
When I switched the company to Black, I reformatted the whole repository history with it. Every developer had to clone the repository again and reapply their local changes to it, but in the end it was a good choice because "blame" still works perfectly since we don't have one big reformatting commit.
- glacials 5y agoAn alternative is to use Git's blame.ignoreRevsFile[1] option to ignore specific commits when calculating blames. The downside is that although you can save the list of commits in the repo, you cannot do the same for the config setting itself, so it calls for some light automation at scale. [1]: https://git-scm.com/docs/git-blame#Documentation/git-blame.txt---ignore-revs-fileltfilegt https://git-scm.com/docs/git-blame#Documentation/git-blame.t...
- terr-dav 5y agoLight automation: https://github.com/ipython/ipython/pull/12091/files https://github.com/ipython/ipython/pull/12091/files
- tr33house 5y agolooks like a `break` is missing after `has_special_comment` becomes True