[CI] Don't do CI stats reporting/failures for PRs targeting feature branches #99668
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
💚 Build SucceededMetrics [docs]Unknown metric groupsReferences to deprecated APIs
To update your PR or re-run it, just comment with: |
|
Pinging @elastic/kibana-operations (Team:Operations) |
tylersmalley
approved these changes
May 10, 2021
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
May 10, 2021
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
May 10, 2021
kibanamachine
added a commit
that referenced
this pull request
May 10, 2021
) (#99690) Co-authored-by: Brian Seeders <brian.seeders@elastic.co>
kibanamachine
added a commit
that referenced
this pull request
May 10, 2021
) (#99689) Co-authored-by: Brian Seeders <brian.seeders@elastic.co>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Feature branches do not run baseline CI, and so they don't have metrics to compare against and will always fail. Example: #99409
We may want to come up with a better solution in the future, such as comparing to the latest commit from an upstream tracked branch (instead of the target branch), but this will at least get PRs targeting feature branches to stop failing.