4 ms·
> What is wrong with simply pushing a "Fix linting issues" in a new commit? Everything. 1. git blame is obfuscated. "Fix lint" is not helpful or relevant. Tel
by paulddraper 2y ago
> What is wrong with simply pushing a "Fix linting issues" in a new commit?
Everything.
1. git blame is obfuscated. "Fix lint" is not helpful or relevant. Tell me what actually changed.
2. git log is noisy. More stuff is harder to read than less stuff, and you're making me read more stuff.
3. git bisect is difficult. Interspersed broken commits requires more time to sift through. (Lint is a poor example, say it's "fix server config")
4. git cherry-pick is tedious. When you copy the dev change to a release branch (let's say you maintain 1.x, 2.x, etc), you must include errata.
- greg0ire 2y ago5. git revert is tedious When one commit turns out to be bad, you can't revert it cleanly because your "Fix linting issues" builds upon it.