Asbjørn Ulsberg

We did have rather serious issues with the MSBuild task and EXE having very different capabilities because they were essentially completely separate codebases. But I agree that MSBuild should not...

Is the bug here that GitVersion fails even though `false` is passed to one of the `/update…` parameters?

I'm not asking about the message, I'm wondering why you're considering it a bug.

Acknowledged! I agree that both should fail.

Improved logging is always welcome. 🙏🏼

GitVersion operates on the basic principle of having **one versionable entity per repository**. Monorepo and similar methodologies is explicitly **not supported**. If you manage to get GitVersion to work in...

That looks interesting, @sebastienwarin. If you are able to rebase those changes on `HEAD` of `main`, add support for file globbing to the path specs, tests for the functionality and...

@marc-mueller, someone would have to take @sebastienwarin's code, rebase it against `GitTools:main` and submit a PR.

@marc-mueller, yes we have [`IGlobbingResolver`](https://gitversion.net/api/GitVersion/IGlobbingResolver/) in place already. You can have a look at the existing `ignore` tests for inspiration: https://github.com/GitTools/GitVersion/blob/c9df1c4f4b3063dbddb295673e28b96542e420a8/src/GitVersion.Core.Tests/IntegrationTests/IgnoreBeforeScenarios.cs#L14-L33

@marc-mueller, please submit a [draft pull request](https://github.blog/2019-02-14-introducing-draft-pull-requests/) so we can discuss the code and figure out its direction within it.