Skip to content

ci: make ci-gate fail fast#20421

Draft
yperbasis wants to merge 3 commits intomainfrom
yperbasis/failfast
Draft

ci: make ci-gate fail fast#20421
yperbasis wants to merge 3 commits intomainfrom
yperbasis/failfast

Conversation

@yperbasis
Copy link
Copy Markdown
Member

Summary

  • ci-gate no longer uses needs: + if: always(), which blocked it from starting until the slowest sub-workflow finished
  • Instead it starts immediately and polls the GitHub API every 30s for sibling job statuses
  • Exits with failure as soon as any job reports failure or cancelled, letting the merge queue dequeue broken PRs minutes earlier instead of waiting for the full CI suite

Test plan

  • Trigger CI on this PR and verify ci-gate polls and reports correctly
  • Verify a sub-workflow failure (e.g. lint) causes ci-gate to fail within ~30s of the failure, not after all jobs finish
  • Verify ci-gate succeeds when all sibling jobs pass

🤖 Generated with Claude Code

yperbasis and others added 3 commits April 8, 2026 16:13
Instead of using `needs:` (which blocks until the slowest sub-workflow
finishes), ci-gate now starts immediately and polls the GitHub API every
30s. It exits with failure as soon as any sibling job fails, letting the
merge queue dequeue broken PRs minutes earlier.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants