Does git commit message matter
Some teams are trying to standardize the format and content of git messages. In my workflow I’m a frequent committer and this will be quite a pain. Do you think git commit messages are important?
git commit -m “TC?”
Squash merge after PR and your prior commit messages won't matter.
I believe the tester should have this responsibility as he should have a full understanding of what is to be changed before merging.
Whoever. If your have the luxury of somebody else to test and commit your code, then okay. The rest of us are responsible for our own work.
It might feel useless as you don't go and reference it on regular basis. It have saved hours during investigations bugs or old code.
Super important
Also important for searching commit history
Very important. Engineers who don't write proper commit messages tend to be junior
Then squash your commits and write the standardized commit message for the combined commit only
Commits are pretty much history snapshots of your code. It's nice to know what that snapshot has at a glance by just looking at commit messages. There's a ton of reasons why you would need to go back. Plus, you're working on a team who needs those details. Wait until you review someone else's commit and need context on why the change happened. Reading a comment vs. finding the person to ask... if they even remember.
It's helpful for getting commit context at a glance, populating messaging in CI tools, and possible integrations with JIRA and other ticketing systems. It's good practice and pretty standard everywhere I've been. If you commit small chunks frequently just do it in a branch, squash and commit one meaningful time with proper messaging before pushing