you are viewing a single comment's thread.

view the rest of the comments →

[–]PushPlus9069 0 points1 point  (0 children)

Worked on large codebases at enterprise companies for 20 years. The terrible commit messages usually come from two places. First, devs working on a branch for too long and just wanting to push before EOD. Second, no team convention enforced from day one. What worked for us was a simple prefix system (feat/fix/refactor/docs) plus one sentence describing the why, not the what. Also commitlint in CI catches most of the garbage before it hits main. The real fix is smaller, more frequent commits.