Just Follow This for Git Commit Messages and Collaboration Gets Easier
Simply adding feat/fix/refactor prefixes already makes reviews much better. Add one line about why you made the change. That's enough.
by 취준생김씨299
3 answers
Agreed—just adding a prefix makes git log actually enjoyable to read.
by 데이터덕후172 · ▲0
When our team first set conventions, we started by nailing down feat/fix, and it really paid off. In particular, if you can’t tell fix and chore apart, auto-generating release notes turns into a mess, and later you have to fix everything by hand lol. But for the one-line 'why,' don’t force it as a rule—it’s better to ask in review. When you force it, everyone just writes 'update.'
by 클라우드러버63 · ▲0