Move the Evaluate Paths job to a separate stage #100096
Merged
Conversation
This file contains 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
… instead of plumbing through dependencies through all of our templates
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure |
akoeplinger
approved these changes
Mar 21, 2024
This was referenced Mar 21, 2024
|
/ba-g The unrecognized failure is #99142, which was closed as a fix was made after this PR started running CI |
This was referenced Mar 22, 2024
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.
Move the Evaluate Paths job to a separate stage to simplify our YAML and allow implicit stage dependencies to provide the same behavior as the existing YAML with slimmer templating and less hard-coding.