Re:Git Rebase for the Terrified
by ratchetclank on Tuesday January 13, 2026 @07:38AM
(#46600188)
I disagree, without this info, I can't easily tell if any commit is part of a feature or is a simple hotfix. I need to rely on the commiter to include the info in the commit message, which is almost always not the case.
[ Parent
| on HN ]
Nothing stops you from doing both renade and merge commits.
Except perhaps crappy gui options in GitHub. I really wish they added that option as a button.
Re:Git Rebase for the Terrified
by pluralmonad on Tuesday January 13, 2026 @12:38PM
(#46604536)
But you are still relying on them to name the branch in such a way it encodes that info. It is unclear why this is superior to messages in commits.
Re:Git Rebase for the Terrified
by globular-toast on Tuesday January 13, 2026 @02:58PM
(#46606950)
It's worse than that: the branch name is lost after a merge. That "merge branch xyz" is simply the default commit message. So it doesn't matter what you do, commit messages are all you have!