docs: improved regex for conventional commit docs

[roverell]

Recent documentation updated to show how to use GitVersion with Conventional Commit notation has a few gaps. This PR is just an incremental improvement.

Description

• Updated regex expressions to support more cases.
• Additional test scenarios to support.

Related Issue

Partial feature implementation discussed in this this PR and this issue (closed)

Motivation and Context

Current docs are incomplete and regex is not consistent with Conventional Commits in some cases.

How Has This Been Tested?

Updated existing tests, replacing with TestCase scenarios for isolation and brevity.
Ran all unit tests in solution successfully.

Screenshots (if appropriate):

Checklist:

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

[roverell]

Would we be open to implementing a (new) config option to opt in to various SemVer commit notation schemes? It would be easier for consumers to switch without having to hide their eyes from regex expressions.

If reasonable I could open an issue and potentially look at implementing this.

[asbjornu]

Would we be open to implementing a (new) config option to opt in to various SemVer commit notation schemes? It would be easier for consumers to switch without having to hide their eyes from regex expressions.

A very closely related where this is being discussed is #2065.

[roverell]

Thanks for the quick reply. I think that one is more about the output version syntax, where this is more about the parsing of the commit message. Still, its along the same thought process of widening the use-cases for GitVersion.

[mergify]

Thank you @roverell for your contribution!

[arturcic]

🎉 This issue has been resolved in version 5.6.7 🎉
The release is available on:

• GitHub Release
• Chocolatey Package
• .Net Global Tool

Your GitReleaseManager bot 📦🚀