Hardy Hobeck

> > I think it is quite common to merge from release to develop and not to master (at least not at the same time). Think about it if you...

> > Another scenario could be if you cancel the hole release or you decide to go back to the alpha phase. > > As long as the `release/*` branch...

> > Okay and why is the TrackMergeTarget property be true per default in the develop branch configuration? (Please see ConfigurationBuilder.cs) > > I don't see how `MergeMessageVersionStrategy` is related...

> > > Okay and why is the TrackMergeTarget property be true per default in the develop branch configuration? (Please see ConfigurationBuilder.cs) > > > > > > I don't...

Here is a better example: ```csharp [Test] public void __Just_A_Test__() { var config = new Config() { VersioningMode = VersioningMode.ContinuousDelivery, Branches = new Dictionary() { { "main", new BranchConfig() {...

> What I mean is that in a support/* branch, you will often alter changelogs, bump version numbers in package.json files and such to match that of the release number....

But still could some one explain me for which scenario the feature track-merge-target is good for or give me a business use case please? > track-merge-target > Strategy which will...

Okay thank you very much for outlining your branching and merging strategy. If I compare your custom workflow with the gitflow workflow then the difference is only how you treat...

In my opinion this issue here is related to the issue #1789 and vice versa and both can be solved with the track-merge-targets feature. But like I have in the...

Please take a look and tell me if you are agree with this test (see integration test [here](https://github.com/HHobeck/GitVersion/blob/feature/3101/src/GitVersion.Core.Tests/IntegrationTests/SemVerOfAFeatureBranchStartedFromAReleaseBranchGetsDecrementedScenario.cs)). Two commits have been pushed after you entered the beta phase that's...