(The ulterior motive here is wanting to give students useful guidance on writing commit messages that’s based on opinions other than my own. Also just curiosity.)
Conversation
Notices
-
Embed this notice
Paul Cantrell (inthehands@hachyderm.io)'s status on Thursday, 27-Feb-2025 01:59:33 JST Paul Cantrell
-
Embed this notice
Jeff Miller (orange hatband) (jmeowmeow@hachyderm.io)'s status on Thursday, 27-Feb-2025 02:08:26 JST Jeff Miller (orange hatband)
@inthehands "When in Rome, do as the Romans do" for commit messages.
The more readers and the more purposes to which the logs are put, the more value in structure. I really like linking a work ticket when apt. Good URLs are marvelous context connectors.
-
Embed this notice
Paul Cantrell (inthehands@hachyderm.io)'s status on Friday, 28-Feb-2025 03:28:45 JST Paul Cantrell
Poll concluded, and the results are mostly unsurprising (or at least roughly align with my own views). Unsurprising, but I do think the results are interesting:
The results show strong consensus that what matters in commit messages is the information content, not the form / format / grammar — yet I keep seeing these •highly• prescriptive commit formatting style guides that are excessively concerned with form, and treat communication as a minor afterthought.
And — and! —
-
Embed this notice
Paul Cantrell (inthehands@hachyderm.io)'s status on Friday, 28-Feb-2025 03:31:05 JST Paul Cantrell
Every time I see one of those overly prescriptive commit style guides, imposter mode kicks in and I think, “Wait, have am I doing it wrong? Have I been doing it wrong the whole time?! Should I adopt this standard?? Should I correct strangers now???”
Next time, I’m going to ground myself in the results of this poll question and stand my groud:
-
Embed this notice
ohmrun (ohmrun@hachyderm.io)'s status on Friday, 28-Feb-2025 03:35:40 JST ohmrun
@inthehands
fix: put 'fix' in my commit messages so it makes it to the changelog
-
Embed this notice