Hardy Hobeck

It is not clear for me what you are actually doing, Could you please give us some steps to reproduce? Or even create a integration test with your expectation? ```csharp...

I have tested your integration test on the PR #3190 and it's working like you would expecting it IMO.

```csharp [Test] public void __Just_A_Test__() { using EmptyRepositoryFixture fixture = new("develop"); var configBuilder = ConfigBuilder.New; // Create commit A on develop fixture.MakeACommit(); // ✅ succeeds as expected fixture.AssertFullSemver("0.1.0-alpha.1", configBuilder.Build()); //...

I'm not sure what your branching and merging strategy is exactly but it seems to be that the gitflow strategy maybe a good solution for you (see gitflow example [here](https://gitversion.net/docs/learn/branching-strategies/gitflow/examples))....

I have taken a look in to the source code of GitVersion in version 5.10.1 and cannot find any usage of the TrackMergeTarget settings. In my opinion this property is...

I have found the following logic changed by Jake Ginnivan in 2015 (see commit [1]): ```csharp public class GitFlowDevelopBranchBaseVersionStrategy : HighestTagBaseVersionStrategy { protected override bool IsValidTag(GitVersionContext context, string branchName, Tag...

I would like to understand the intention of the TrackMergeTarget property. @asbjornu May be you can give me your opinion about the following scenario: ```csharp [Test] public void __Just_A_Test__() {...

I'm also thinking about it in which circumstances the MergeMessageVersionStrategy is used in the gitflow worflow. Cannot find any scenario. Maybe it is good for the github workflow with continues...

> Why would a `release/*` branch be merged to `develop` but not to `master`? Shouldn't those merges be done at the same time and either both or none of the...

> I would recommend against its use for any other workflow than trunk based development aka `mode: Mainline`. Okay and why is the TrackMergeTarget property be true per default in...