Thanks for the reply!
I try to follow the small commits approach and set the specific files involved in the commit message to have a track about the subject.
This. It's impossible to write a good commit message if you are committing 273 changes accumulated over a week. Always organize your commits into small self-contained units to begin with. Only then would you be able to write precise and concise commit messages.
Thanks for the reply!
I try to follow the small commits approach and set the specific files involved in the commit message to have a track about the subject.
This. It's impossible to write a good commit message if you are committing 273 changes accumulated over a week. Always organize your commits into small self-contained units to begin with. Only then would you be able to write precise and concise commit messages.
I totally agree with you.
When we start to break in smaller pieces it starts to make more sense the commit messages in intersection of files staged.