3 ms·
> Making commits that don’t compile, don’t pass tests, or don’t run is useful. I'm not sure I agree with you there on that one.
by Karellen 4y ago
> Making commits that don’t compile, don’t pass tests, or don’t run is useful.
I'm not sure I agree with you there on that one.
- sulam 4y agoAn example is renaming a method that’s heavily used. It can be nice to have the first commit be the rename, and then the second commit be changing the usages. When you code review that, it makes your job easier. Trivial example but you can work up less trivial ones from there.