Asbjørn Ulsberg

@corentinvds, we could make such backwards-incompatible changes in v6. I think it makes sense that all `ignore` properties lead to the ignored commits to be excluded from all version calculation....

Seems like we don't have a test for `-diag` at all. I suppose the bug may be that `-config` is parsed as a value for `-diag` somehow. It should be...

If you change the switches from slash (`/`) to dash (`-`), does the behaviour change?

This is strange. As you can see by the following test, `-verbosity Normal` should work. We should probably add a `TestCase` for the other verbosity levels as well. https://github.com/GitTools/GitVersion/blob/17cf0dff4210ff3622a3bbc461e9bb367e9db74a/src/GitVersion.App.Tests/ExecCmdLineArgumentTest.cs#L39-L53

It's possible that for the specific code path, there is no difference between `Normal` and `Verbose`. You would have to dig into the source code and see whether it logs...

I agree that having GitVersion output a log that more clearly points out why it has made a decision and its effects on the version number would be highly beneficial....

I get it. I'm just not sure the switch is broken or that there are more details to be exposed.

I'm able to reproduce this on macOS 11.7.1. Seems like our test coverage for the `-c` argument is poor. I don't use the `-c` argument myself, so I don't have...

Sure, we could expose something like that as a variable. Pull requests are welcome!

If `GitVersion.Tool` gives you the version number you want, why do you want to use `GitVersion.MSBuild`? You can try to [configure the MSBuild task](https://gitversion.net/docs/usage/msbuild). Setting `UseFullSemVerForNuGet` to `false` should yield...