3 ms·
> if everybody is reformatting it’s doesn’t really matter how much. Really aggressive reformatting introduces git blame horizons that can make code archaeology
by bunderbunder 8y ago
> if everybody is reformatting it’s doesn’t really matter how much.
Really aggressive reformatting introduces git blame horizons that can make code archaeology more annoying.
I wouldn't consider it a reason not to switch to autoformatting, but it might be a reason not to get too wild about changing the conventions.
- hinkley 8y agoIt's why I issue a separate commit for reformatting. At least when the person sees my commit in git blame they know to annotate the previous version.
- notduncansmith 8y agoOr even better, do it once for the main codebase in a single commit, then make sure developers have their editors apply the formatting on save, and a formatting check in CI, so that way misformatted code never gets code-reviewed.