Asbjørn Ulsberg

>Thank you very much it is a pleasure for me to give some innovation back to this project. My customer uses this tool and gave me time for this bug...

Which version of GitVersion are you experiencing this with? Have you tried upgrading to the latest v5 beta?

It's very hard to know without being able to reproduce the problem. A public repository portraying this issue would help immensely.

Great find, @samjwest. A PR that adjusts the default regex of GitVersion to also match AzDO's out of the box would be welcome.

@owns, as I don't use AzDO myself, nothing is going to happen until someone who actually needs this submits a PR, as noted in https://github.com/GitTools/GitVersion/issues/1579#issuecomment-587471184.

@joaorosado, I think the real problem here is AzDO failing on warnings being logged and not on the exit code of the executing process. Or is the exit code of...

I'm a bit uneasy about all the removed and modified tests. I would also like @ibvhefe to take this PR for a spin to see if it solves their issue.

@ibvhefe thanks for the provided test. Does it fail on @rominator1983's [`fix/IgnoreAllCommits_Issue3074` branch](https://github.com/rominator1983/GitVersion/tree/fix/IgnoreAllCommits_Issue3074) or on `GitTools:main`?

First remove `next-version: 2.0`. If that has no effect, then great; less configuration. If it doesn't help increment the release branch to `2.1` then try to [configure](https://gitversion.net/docs/reference/configuration) `increment: Minor` and...

It sounds like you have a different problem, @Ksdmg. `release/ICO-5-release-v1.1.0` producing the version number `5.0.0-beta.1` sounds like an unintended match on the `5` in `ICO-5` and not related to the...