Asbjørn Ulsberg

Adding a test shouldn't require deep knowledge about the GitVersion codebase. They are pretty straight forward: https://github.com/GitTools/GitVersion/blob/e8102abf08381bcc4d7514df1bd9f57db6bc29fd/src/GitVersionCore.Tests/IntegrationTests/VersionInTagScenarios.cs#L33-L52 Start with writing a test that provokes the behaviour you're experiencing, then you...

Sorry, but writing code in a comment is not the same as submitting a draft pull request, @DocZoid.

Sorry, but the constructive feedback is very hard to give on an island of code like that. If I had a proper draft pull request to look at, I would...

You can read about how to [fork a repository](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo) and then how to [submit a pull request from a fork](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork).

A separate branch would be best, as a pull request is not frozen in time, so whenever commits are added to the branch you create the pull request from, they...

Thanks for the PR and test, @DocZoid. It is a great way to understand your use-case. From what I understand, you would like `release` branches to always yield the pre-release...

Sorry for not answering this before, @DocZoid. > Actually we are using Git Flow, but only as a branching model, not using the commands. I too use Git Flow "manually"...

@NatMarchand, thanks for the detailed explanation. Is the following pseudocode a fair description of what's happening? ```cs var semver = new SemVer("0.2.0"); var taggedSemanticVersion = new SemVer("0.2.0-alpha.0"); if (semver.CompareTo(taggedSemanticVersion, false)...

It seems like this may be a duplicate of #2241.

Remove `next-version`, add a `git tag 3.0.0` on an appropriate commit and try again, please.