[taeric]

Honestly, sometimes I'm fine with a single line passed to -m for the command. I don't have a hard rule that all commits must have an email attached to them.

However, unless the single line is "fix typo" or some such, often I'm very interested in why code has been sent up for review. And don't just tell me what you did, but why you did it. If I get one more "increased the retry policy" style messages that doesn't expand on why a downstream component needs us to retry more, I'm going to go insane.

A sister team of mine has gone so far as to templatize this. I'm very sympathetic to the idea, but I don't support it yet. I think I'm coming around, though.

[duncan-donuts]

I'm too used to seeing "updates" or "<JIRA_ID>". It's insanity. I wish we could get a common understanding let alone a template.