Asbjørn Ulsberg
Asbjørn Ulsberg
@HHobeck as I suspected. So it is the repository normalization that is causing this problem, which I thought was fixed. Oh well.
As I wrote in https://github.com/GitTools/GitVersion/discussions/4183#discussioncomment-10484112: > It seems like this is related to #2074, #2456, and #4015. I think what GitVersion needs to do is a ref-check of the checked...
Closing as duplicate of #4212.
> Can I just do a squash commit/rebase to tidy the commits up - surely you do a squash on merge anyway? No, we don't do squash merge commits. We...
> Also, not sure how to address the flaky windows/qodana builds No, it seems unrelated to this PR. I'm hoping @arturcic has an idea.
Sorry, but I don't quite understand what you're suggesting @9swampy. I think what you've done so far in #4657 looks good, but the failing tests are of course a concern....
In normal working conditions, the expected output from GitVersion is a full and valid JSON document. Writing log messages to stdout would break this. I’m not sure what we can...
> 1. What was the reason for the breaking change from 6.2 -> 6.3? @otac0n, sorry, I was not aware that this was a breaking change in 6.2 (I assumed...
@HHobeck, I think these changes look reasonable. What are your thoughts on this?