performance pipelines triggers unified #113556
Merged
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
e-kharion
added
the
perf-pipeline
e-kharion
requested review from
DrewScoggins,
LoopedBard3,
matouskozak and
caaavik-msft
dotnet-issue-labeler
bot
added
the
needs-area-label
caaavik-msft
approved these changes
Mar 14, 2025
matouskozak
approved these changes
Mar 15, 2025
| @@ -15,10 +15,10 @@ trigger: | |||
| include: | |||
| - main | |||
| - release/9.0 | |||
| - release/8.0 | |||
There was a problem hiding this comment.
How often do we run microbenchmarks on non-main branches? It seems like we mostly look at data from main anyways.
There was a problem hiding this comment.
I'd think that it's very rare
matouskozak
added
area-Infrastructure
and removed
needs-area-label
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.
No description provided.