[EPAC-2009]: dedup CI failure Linear issues#578
Merged
riddim-developer-bot[bot] merged 1 commit intoMay 25, 2026
Merged
Conversation
riddim-developer-bot
Bot
deleted the
symphony/epac-2009-dedup-by-workflow-name-branch-comment-on-existin
branch
May 25, 2026 05:41
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.
Why
Flapping GitHub Actions workflows can create multiple urgent Linear issues for the same failing workflow and branch. This keeps one open
ci-failureissue as the signal and records subsequent runs as capped comments.What changed
[CI] {workflow_name} failing on {branch}titles.ci-failurelabel.Trade-offs not taken
Test plan
python3 -m pytest scripts/ci/tests/test_ci_failure_to_linear.py -qpython3 -m pytest scripts/ci/tests -qSkipped external gate: release-manager manual validation still needs to inject 6 consecutive failures of the same workflow on main and verify the expected single issue/comment-cap behavior.
Reviewer-Boundary: review-only
Resolves EPAC-2009