← Back to context Comment by PUSH_AX 9 hours ago Fine, but none of that is in a normal commit message, lets be real... 7 comments PUSH_AX Reply mgfist 8 hours ago Which circles back to why it's important for leadership to tackle this PUSH_AX 8 hours ago Yes, but not in the form of commit messages, the parent comment described things better suited to jira tickets, documentation etc.It feels like we're trying really hard to stretch the utility of commit messages here... macintux 7 hours ago Mainly I was pushing back on: the code is the "truth"I don't feel that is an accurate statement for any complex system. 3 replies → cratermoon 6 hours ago You'll at least need the discipline to include the ticket ID in the message. Links to documentation are ok, but they will likely rot and even if they don't the content may change such that it no longer accurately reflects the commit changes.
mgfist 8 hours ago Which circles back to why it's important for leadership to tackle this PUSH_AX 8 hours ago Yes, but not in the form of commit messages, the parent comment described things better suited to jira tickets, documentation etc.It feels like we're trying really hard to stretch the utility of commit messages here... macintux 7 hours ago Mainly I was pushing back on: the code is the "truth"I don't feel that is an accurate statement for any complex system. 3 replies → cratermoon 6 hours ago You'll at least need the discipline to include the ticket ID in the message. Links to documentation are ok, but they will likely rot and even if they don't the content may change such that it no longer accurately reflects the commit changes.
PUSH_AX 8 hours ago Yes, but not in the form of commit messages, the parent comment described things better suited to jira tickets, documentation etc.It feels like we're trying really hard to stretch the utility of commit messages here... macintux 7 hours ago Mainly I was pushing back on: the code is the "truth"I don't feel that is an accurate statement for any complex system. 3 replies → cratermoon 6 hours ago You'll at least need the discipline to include the ticket ID in the message. Links to documentation are ok, but they will likely rot and even if they don't the content may change such that it no longer accurately reflects the commit changes.
macintux 7 hours ago Mainly I was pushing back on: the code is the "truth"I don't feel that is an accurate statement for any complex system. 3 replies →
cratermoon 6 hours ago You'll at least need the discipline to include the ticket ID in the message. Links to documentation are ok, but they will likely rot and even if they don't the content may change such that it no longer accurately reflects the commit changes.
Which circles back to why it's important for leadership to tackle this
Yes, but not in the form of commit messages, the parent comment described things better suited to jira tickets, documentation etc.
It feels like we're trying really hard to stretch the utility of commit messages here...
Mainly I was pushing back on: the code is the "truth"
I don't feel that is an accurate statement for any complex system.
3 replies →
You'll at least need the discipline to include the ticket ID in the message. Links to documentation are ok, but they will likely rot and even if they don't the content may change such that it no longer accurately reflects the commit changes.