fix!: no-bump-message now takes precedence over *-version-bump-message.

[jeanplevesque]

Description

This PR changes the behavior of commit-message-incrementing when using commits that matches both *-version-bump-message and no-bump-message. no-bump-message now takes precedence over *-version-bump-message.

Previous Behavior

Commits that match both *-version-bump-message and no-bump-message use the highest increment associated with *-version-bump-message.

New Behavior

Commits that match both *-version-bump-message and no-bump-message don't have an increment.

Related Issue

Resolves #3172.

Motivation and Context

Repositories that enforce conventional commits along with commit-message-incrementing (with a config like this) can now have commits that don't have version bumps.

Example:

chore: Adjust .editorconfig for coding convention.
+semver: skip

How Has This Been Tested?

An integration test was added to ensure the new behavior is covered by tests. The newly added test fails when reverting the changes.

Checklist:

• [x] My code follows the code style of this project.
• [x] My change requires a change to the documentation.
• [x] I have updated the documentation accordingly.
• [x] I have added tests to cover my changes.
• [x] All new and existing tests passed.

[jeanplevesque]

Do you feel like this is ready for review now, @jeanplevesque?

Yep! 😀

[mergify[bot]]

Thank you @jeanplevesque for your contribution!