A big part of our job as developers is communicating with each other.
Squashing/Rewording commits is a low time investment to improve said communication and the code reviewing process.
Having a clean commit history also allows us to find commits that might have introduced bugs and enable rollback if necessary.
Example of commits which we might want to reword or squash:
A big part of our job as developers is communicating with each other. Squashing/Rewording commits is a low time investment to improve said communication and the code reviewing process. Having a clean commit history also allows us to find commits that might have introduced bugs and enable rollback if necessary.
Example of commits which we might want to reword or squash:
For more info on squashing/rebasing to improve our commit history, here's a step-by-step guide: https://medium.com/@vanshbadkul/squashing-commits-in-git-a-step-by-step-guide-884581224adf