On Thu, 23 Oct 2025, Renee Otten wrote:
(re-sending to list, this time using the correct e-mail account so the message doesn’t bounce)
It didn't bounce here.
I probably squash-merged the PRs and indeed I felt/feel that all the additional text in the commit message is superfluous.
I see no reason to be stingy with commit messages when anyone who wants the short-form view can just specify --oneline in the command. I never would have gotten away with such short CL descriptions at Google.
Commit messages complement code comments. The latter explain why the code is the way it is; the former explain how it got there and why.
It's been a long-standing tradition for Ruby updates to include a link to the upstream release announcement; that was part of what was removed. I only just yesterday determined the proper similar link for asciidoctor.
Squashing isn't supposed to truncate commit messages anyway, though perhaps GitHub has a weird interpretation. Squashing with the command-line tool presents a concatenation of all the included commit messages, to be edited into something appropriate for the combined commit. Though squashing a single commit isn't even possible from the command line.
Fred Wright
