Distinguish merge commits when checking commit message.

[donquixote]

Q	A
Version	GrumPHP 0.15.2
Bug?	no
New feature?	yes
Question?	no
Documentation?	no
Related tickets

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. vs Issue #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!

[veewee]

Currently the merge patterns are ok. I agree that it allows you to bypass the system, but so does adding the -n option to a git commit.

In order to detect if current commit is an acutal merge commit, additional git commands need to be executed. (Checking if the commit contains multiple parents).

Feel free to provide a solution for this.