This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Distinguish merge commits when checking commit message. #730
Labels
You can continue the conversation there. Go to discussion →
class CommitMessage analyses if the commit message matches a given pattern. The exact rules can be configured.
Typically, a merge commit will have a different commit message than a regular commit.
E.g.
Merge branch 'a' into b.
vsIssue #55: Add more tests.
.Currently grumphp does not distinguish between actual merge commits and regular commits.
This means it is possible to (accidentally) name a non-merge commit like
Merge 'a' into b.
without grumphp complaining.It would be great if grumphp could distinguish between these cases.
If we want to be excessive we could also distinguish multi-parent commits :) but let's not overdo it!
The text was updated successfully, but these errors were encountered: