Repository navigation
T-22072 [CI] Keep the E2E Linear issue short and free of tables - #9
Merged
Merged
Conversation
A failed job's summary goes into the issue in place of its errors, which only fill in for a job that stopped before writing one, once each. Summaries list their numbers as bullets, since Linear renders wide tables poorly. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
The E2E Linear issue said the same thing up to three times per failed job: the job's errors, then the same errors as ❌ lines under each read-back. Its tables are hard to read in Linear.
notify_linear_failure.ymladds a failed job's summary or, when the job has none (it stopped before writing one), its errors, without duplicates. Callers that set neither input still get the plain issue.🤖 Generated with Claude Code