Asbjørn Ulsberg

Why are you unable to use `git tag`?

Why would you need to use `git tag` on every build? Do you change the value of `next-version` on every build?

> No, but if I remove `next-version:` from the Gitversion.yml, which version will be used? The highest `git tag` GitVersion can find from the current branch. If you add `git...

Sounds good. Can this be closed, then?

You may try to configure [`source-branches`](https://gitversion.net/docs/reference/configuration#source-branches) for `develop` to include `release`.

Because `release` is not a source branch for `develop` by default, and configuring it as such may force GitVersion to consider the tag on `release` when calculating the version for...

Seems like the `1.3.0-beta.1` tag on `release/some_release` is not considered when computing the version on `develop`. The "proper" way to do it is to apply tags to `main` or `master`....

Well, the expectation is to be able to use the branch name as a version source both when it exists and its presence in the merge message once it’s been...

Thanks for the feedback @svengeance! I agree with you and will adjust my examples (moved to #2275) accordingly.

Sorry for allowing this to become stale without responding. I think this is related to what's being discussed in #2065.