News for hackers. Stuff that matters.
Re:How to write a Git commit message (2014) by darylteo on Wednesday May 04, 2022 @07:13PM (#31267086)
Your commit topic shrinks to only 40-45 characters if you try to do both (card numbers get quite large too if you're in a jira context, with their issue prefixes PROD-001 is 8 characters already) so you pick and choose.

The other thing is that in an internal context, what does knowing whether it's a feature or a bugfix do for you? If it's such a big issue, then it'd be integrated into the issue prefix

BUG-001

FEA-002 < less likely as each feature epic will probably have it's own code, so it'll be more XXXX-001 XXXX-002

Now you have a nice short log that aligns nicely, and you can figure out mostly where your merge points were anyway, so no need for merge commits, rebase works mostly fine.

- BUG-001 fix for this thing

- FEA-005 initial commit

- FEA-005 unit tests

- FEA-005 implement this thing

- FEA-005 implement that thing

- FEA-005 fixes for code review

- BUG-002 fix for another thing

- BUG-002 revert fix did not work

- BUG-003 fix for that annoying thing

Of course, just my 2c and my limited personal experience.

There are no comments on this comment yet.