Git Commit Practices
The cluster debates the best practices for git commits, focusing on whether developers should make small, frequent commits or larger ones, with discussions on code review, hygiene, and workflow efficiency.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Have you considered making smaller, more frequent commits.
What's wrong with a single commit for a feature?
Is "more frequent commits" really a good thing?
...you really should not be going days between commits...
This is not good practice in many circumstances. Large commits are very hard for others to review.
If the commits don't matter why did you make them separate to begin with?
That's just bad git hygiene, and lots of lead devs deal with this across the development world. One change per commit/PR please.
Rest assured, anyone not committing (or stashing) often and squashing down is doing it wrong.
Large commits are an antipattern that should be reworked, in code review at worst.
Is it really that many developers who don't split up their code into seperate commits?