Hacker News Reader

I respectfully disagree. Regardless of branching model, why not use commit titles like:

`{Jira-1234} ADD flux capacitor control module`

... and put more verbose details in the commit message body if/when needed?

I think the opposite tends to be more helpful. The title should give you as much information as possible at a glance since it's likely to be seen in a list of commits or as part of the history of a file or line of code.

The more verbose details and ticket id should be in the body since I'm more likely to care about them once I've pulled up the commit to review in detail.

Not to belabor the point, but once you're familiar with the contents of a given ticket (the "{Jira-1234}" reference in my example), the commit message titles' information density goes way, way up. Adding this ~12-character prefix results in useful, scannable, one-line commit messages. I see no downside.

Reply on news.ycombinator.com