Asbjørn Ulsberg

Is `feature/jenkins/branch-nameA` an actual branch name or is it just there as an example?

I was just wondering whether the branch names had upper and lowercase letters in them, because that is a known source of problems for mixed Windows/Linux environments.

Then that may definitely be the cause of this bug, as `feature/NAN-2222` would be considered a different branch (and physical directory on disk) to `feature/nan-2222` and `feature/NaN-2222` on most Linux...

I understand, but there's nothing we can do in GitVersion to avoid this. You will have to build some checks before running GitVersion that does some case-insensitive checks on branches...

Why are you setting `is-mainline: true` on your `release` branch in the first place?

Try `increment: Patch` and [`mode: ContinuousDeployment`](https://gitversion.net/docs/reference/modes/continuous-deployment).

Correct, it is only `CommitsSinceVersionSource` that increments on commits. `increment: Patch` only tells GitVersion to increment patch in relation to the version source (usually the last `git tag` on `main`)....

> Having gitversion set environment variables `GITVERSION_[NAME]=value` be helpful. `gitversion /setenvironmentvariables` Adding a switch for it doesn't make much sense since GitVersion already does this automatically on build servers. Are...

I understand. Thank you for taking the time to write up such a thorough test. However, unless I've done something very strange, the test succeeds if you add the `fixture.Repository.MakeATaggedCommit("1.0.0");`...

It is absolutely the case that `next-version` **should** give you the behavior you expect. Unfortunately, there is something in the handling of `next-version` that makes it not work like a...