Repository navigation
fix: clarify attention filter during outages - #1378
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Clarify the Jobs attention-filter warning so it explains that incomplete monitoring summaries can still show known attention reasons. Add regression coverage for unavailable summaries with a known failed attempt and with no known attention reason, and document the behavior in the Jobs guide.
Closes #1377
Validation:
npm run lint,npm run build,npm run test:coverage(623 tests and coverage gates),npm run test:e2e(160 passed, 272 skipped), andnpm --prefix docs ci && npm --prefix docs run build. Independent browser review passed at desktop and 320px widths.