Hardy Hobeck

This issue is all about the following line within the class `BranchConfigurationCalculator`: ```csharp this.log.Info($"No branch configuration found for branch {targetBranch}, falling back to default configuration"); ``` The branch configuration system...

I have taken a look into the code and saw unit tests which are testing the behavior as following: ```csharp private static readonly object?[] GitHubPullPullMergeMessages = { new object?[] {...

@ooredm To workaround this I would suggest you to change the configuration and place the following string: ```yaml merge-message-formats: Custom: '^Merge pull request #(?\d+) (from|in) (?:[^\s\/]+\/)?(?[^\s]*)(?: into (?[^\s]*))*' ```

Actually I don't understand the statement that fast-forward merges messes up version calculation in combination with the behavior generating sporadicly a different version. Of course in some situation using fast-forward...

To understand your request: Do you think a change of the existing code is necessary as well (change classes from internal to public) or is it just to publish the...

I'm not sure if it is a bug or feature. Anyway I see your use case. When merging from master to develop why not just do a rebase?

> Hi @HHobeck . > > Do you mean rebase of `develop` over `master`? That's not an option as there are many developers working on new features, and all of...

> Thank you for your reply! Interesting option with rebasing, but we would prefer not to rewrite the history of our develop branch. Is there any other option built-into GitVersion...

I think we need to revert it. The fix is not right unfortunately.

Only this one needs to be reverted: https://github.com/GitTools/GitVersion/pull/3927/commits/a0c170b19dc5254338d675b9c2eb0aa8ee529680