3 ms·
If you keep all the intermediary commits, it's pushing more process onto the dev in the middle of coding. Some people may do this well, but more often than not
by another-dave 4y ago
If you keep all the intermediary commits, it's pushing more process onto the dev in the middle of coding. Some people may do this well, but more often than not I do just see "WIP (test broken)" etc.
With a squash/rebase, the development has to write an accurate commit message once & they're doing it when they've fully understood the solution they've written.
- seba_dos1 4y ago> it's pushing more process onto the dev in the middle of coding Uhm, how exactly? Splitting & merging things into sensible, atomic commits with proper commit messages is usually what you do right before pushing it out for someone else to see, definitely not "in the middle of coding".
- eurasiantiger 4y agoIt doesn’t seem logical to me that someone working on solving an intellectual puzzle would do so without having a consistent internal narrative of what they are doing. If a developer can’t fit their change description on one line or don’t even know where to start describing the changes, chances are they could commit much more often. The way I see it, a commit message like ”WIP (test broken)” is unprofessionalism bordering on self-sabotage.