[Feature] Introducing a new branch related property with name track-merge-message

[HHobeck]

Is your improvement request related to a problem? Please describe.
In the discussion of issue #3052 ([Bug] track-merge-changes produces unexpected result [..]) I came up with the idea of introducing a new branch related property with the name track-merge-message (see #3052 (comment)).

Detailed Description

Consider we have a main branch and a release/1.0.0 branch and merge changes from release/1.0.0 to the main branch. Then this commit message will be interpreted when executing the tool on the main branch as a next version 1.0.0. I would like to make it configurable so you are able to change this behavior with track-merge-message e.g. on the main branch to false. This gives you the next version 0.0.1 instead of 1.0.0.

Context

This property fits like all other branch related properties into the configuration system and gives the user the possibility to control the behavior of whether the merge commit message will be interpreted as a next version or not. Today the message will be always interpreted as a next version which can be in some workflow scenarios not what you want.

Possible Implementation

I think the implementation is not hard because we only need to check this property in the class who implements this aspect of the VersionStrategy.

[arturcic]

🎉 This issue has been resolved in version 6.0.0-beta.1 🎉
The release is available on:

• GitHub Release
• Chocolatey Package
• .Net Global Tool

Your GitReleaseManager bot 📦🚀