mirror of
https://github.com/conventional-commits/conventionalcommits.org.git
synced 2026-03-22 12:44:37 -05:00
Merge Commit guidelines #81
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @fallion on GitHub (Sep 11, 2019).
For merge commits how lenient are conventional commits? Can a tool for checking conventional commit compliance simply find the
Mergekeyword and allow anything after that?https://github.com/commitsar-app/commitsar/issues/101
@wesleytodd commented on GitHub (Sep 30, 2020):
I think this is tricky, because technically a merge commit is any commit with more than one parent. I have edited a merge commit message and not kept the
Mergekeyword. I don't know how common this is but I feel like any opinions here might be better left to the tooling than added to the spec.If a tool wants to get very technical about it, it can run something like
git rev-list -1 --merges HEAD~1..HEADto see if the commit is a merge commit. Since the spec and parser do not have opinions on underlying git features (or even git as the scm at all), I think maybe it is best to follow the guidance on reverts and leave it up to tools.