How to increment version from commit/merge message ONLY?

[v1ferrarij]

Hello,

I am looking to use GitVersion to version our modules.

I basically only want GitVersion to bump the version depending on the LAST COMMIT/MERGE message.

For example, when we merge a PR, the default message will contain the branch name Merged PR 54: feature/example

All I want Gitversion to do is read this and then increment the version, in the example above the next version would be 0.1.0

I currently have this setup but it is not performing as expected.

mode: ContinuousDeployment
increment: Inherit
major-version-bump-message: '(major|breaking)[\/\\]'
minor-version-bump-message: '(minor|feature)[\/\\]'
patch-version-bump-message: '(fix|patch)[\/\\]'
commit-message-incrementing: MergeMessageOnly
branches: {}

How can this be done, is it even possible?

Many Thanks!

[HHobeck]

For this you need to use the mainline version strategy which is included in the TrunkBased/preview1 workflow:

workflow: TrunkBased/preview1
mode: ContinuousDeployment
major-version-bump-message: '(major|breaking)[\/\\]'
minor-version-bump-message: '(minor|feature)[\/\\]'
patch-version-bump-message: '(fix|patch)[\/\\]'
commit-message-incrementing: MergeMessageOnly
branches:
  main:
    increment: None

Link[1]:
https://gitversion.net/docs/reference/configuration#snippet-/docs/workflows/TrunkBased/preview1.yml

[v1ferrarij]

Hi @HHobeck

Thanks for that, this works.

One thing I have noticed though, take the below example:

1.0.0
Merged PR 1: feature/foo1
1.1.0
Merged PR 2: patch/foo2
1.1.1
Merged PR 3: patch/foo3 (pipeline fails for whatever reason so tag on repo is not created)
Merged PR 4: patch/foo4 (pipeline works)
1.1.3

I am guessing this is expected behaviour, but is there anyway to get GitVersion to only look at the last tag and bump ONLY from the LAST merge message, rather than reading ALL merge messages from the last tag?

[HHobeck]

I am guessing this is expected behaviour, but is there anyway to get GitVersion to only look at the last tag and bump ONLY from the LAST merge message, rather than reading ALL merge messages from the last tag?

No this is not possible. I think the missing piece is the support of merge message bumping in GitFlow/v1 and GitHubFlow/v1workflows (to be more concrete in the MergeMessage version strategy).

Please see following comment #4217 (reply in thread):

I don't see any reason why not implementing it in the MergeMessage version strategy as well:

I invite you to implement this aspect and create a pull-request.

[v1ferrarij]

Hi @HHobeck

The solution above is no longer working anymore, has something changed?

It appears as though it is just ignoring the last tags and now basing the version of the amount of commits since the last tag?

[HHobeck]

What do you mean? The TrunkBased/preview1 workflow is behaving different after the release of 6.1.0? IMO nothing has changed.