DEV Community

Discussion on: What are your WORST git fails?

nombrekeff profile image
Keff Author

Cool, I've been following a similar approach.

I encourage and prefer loads of small & descriptive commits, or not even that descriptive, just enough for me to understand the PR, commits + description. Then we squash the commits down to a more generalized one and clean up the commit description list (remove weird commits messages, fix typos, etc...) in the end I hope that if the squashed commit message is not understood, you got to the PR and check more in detail what has changed.