Asbjørn Ulsberg

I see. Perhaps it should be mentioned in the documentation that `versioning: Semantic` leads to a `git fetch --unshallow`? Some logging from within `Versioning.isShallow()` would also be useful. https://github.com/game-ci/unity-builder/blob/5ba81971e2e97bbbb807a2621c8e6e79cd739d18/src/model/versioning.ts#L179-L183 It...

Oh, reading the code, I see that first a `git fetch --unshallow` is invoked. If it fails, it only leads to a warning. However, a regular `git fetch` is performed...

@jiasli: > > Could someone point us at the suggested new syntax instead of `--sdk-auth`? > > You may simply use the original output without `--sdk-auth`. No, that doesn't work...

Thanks for the information, @NerminMaric! Pull requests to have `Microsoft.Bcl.Async` removed are welcome.

Thanks for providing a reproduction, @HHobeck! It would be interesting to hear what @mmisztal1980 expects the version to be in that scenario.

Thanks for digging out the problematic piece of code, @HHobeck. That is indeed fragile. I would assume we can replace `.Contains("refs")` with `.Contains("refs/")` at least?

Yea, that seems quite wonky. If we could just use `ReferenceName.cs`, that would be much better.

@HHobeck, I think it's debatable whether GitVersion should always try to produce a version number, even in obvious invalid circumstances (such as the repository having no reachable commits, missing `.git`...

@ChristoWolf, no such option exists. Running GitVersion once on the CLI for an entire repository is the recommended workaround.

Sure, but we are also trying to close down the development of v5 to focus on v6. So unless it's very important, such as a security fix or similar, we...