Asbjørn Ulsberg

It may be that the version number in `hotfix` is not considered. Try setting `is-release-branch: true` for `hotfix` in [the configuration](https://gitversion.net/docs/reference/configuration).

@NightFox7, please have a look at the discussions in #3101 and #3190. I think they are relevant for your use-case.

Hm. The accompanying issue (#3020) that this PR is supposed to be resolved was closed by merging #3190. Both #3020 and #3190 are also targeting v6 (`main`), while this PR...

Are you able to reproduce this in a `RepositoryFixture` test akin to the following and submit it as a pull request? https://github.com/GitTools/GitVersion/blob/fe2e24b427f224e3b6dd855b77d957a2e04286d3/src/GitVersion.Core.Tests/IntegrationTests/FeatureBranchScenarios.cs#L82-L94

> I was not able to reproduce the issue within a test. I just found out that problems might be caused be the fast-forward merges that I was using. Yes,...

I suppose we could introduce a new `mode` for it, but I'm not sure what it should be called or how it should work. Do you have any suggestions?

A `mode` in GitVersion corresponds to how you use Git. If you don't use Git in one of the recommended ways (Git Flow, GitHub Flow, Mainline, etc.), you can't expect...

@JohanSpannare, fast-forward merges messes up version calculation royally, yes. Unless you're using `mode: Mainline` and trunk-based development, I would strongly recommend against using it.

I would love to snap my fingers and have this problem fixed, but it doesn't affect me and I have more than enough other things to do, so I neither...

You may be affected by #3041. Please have a look and let me know.