This repository was archived by the owner on Jan 23, 2023. It is now read-only.
Add servicing configuration (build skips) for targeting packs #8824
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
dagood
added
area-Setup
post-consolidation
ViktorHofer
added
the
* NO MERGE *
|
Thank you for your contribution. As announced in #27549 the dotnet/runtime repository will be used going forward for changes to this code base. Closing this PR as no more changes will be accepted into master for this repository. If you’d like to continue working on this change please move it to dotnet/runtime. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
For https://github.com/dotnet/core-setup/issues/8735. Uses dotnet/arcade#4318.
Holding off on merging. Marking post-consolidation to avoid extra migration effort. I'm filing the PR here to keep track of the need to port it over and put it in context. I can't file the PR in the consolidated repo yet because the tooling isn't up to date there. There's no rush: this specific PR has no effect until the stable 5.0.0 build.