[release/3.1] Add flexible baseline patterns: avoid updating online baseline with each release #1752
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This ports the flexible baseline feature from dotnet/arcade#6155 back to dotnet/source-build. This makes servicing updates a bit more sustainable by removing the need to always update the online baseline even if the changes are expected and predictable. See #1726.
I reverted some changes because dotnet/source-build works a little differently. E.g. here, warnings are allowed, and we always know where the baseline is located.
Also, yet another tweak to make VS work for editing the task project. The
*wildcard wasn't evaluating properly with the last attempt because it was put directly into item metadata--now it's simpler.