3 ms·
Not everyone develops and commits the same way and mandating squashing is a much simpler management task than training up everyone to commit in a similar manner
by TheGRS 10mo ago
Not everyone develops and commits the same way and mandating squashing is a much simpler management task than training up everyone to commit in a similar manner.
- esafak 10mo agoBesides, they probably shouldn't make PR commits atomic, but do so as often as needed. It's a good way to avoid losing work. This is in tension with leaving behind clean commits, and squashing resolves it.
- gbear605 10mo agoThe solution there is to make your commit history clean by rebasing it. I often end my day with a “partial changes done” commit and then the next day I’ll rebase it into several commits, or merge some of the changes into earlier commits. Even if we squash it into main later, it’s helpful for reviewing.
- sallveburrpi 10mo agoWe also do conventional commits: https://www.conventionalcommits.org/ https://www.conventionalcommits.org/ Other than that pretty free how you write commit messages