ci: run no job at all on draft pull requests - #1744
Merged
Merged
Conversation
Even three light gates per draft is too much when a swarm opens 130 drafts in ten minutes: 113 CI runs queued ahead of the release publish and the release-please refresh. A skipped job costs no runner, and every guarded job reads scope-gate's outputs, so skipping scope-gate on a draft skips the run. Marking the PR ready or adding ci-full still runs everything it earned.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
This was referenced Sep 18, 2026
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.
Follow-up to #1581/#1592. At 07:17–07:21 another lane opened ~130 draft PRs ("test(mcp): prove tracedecay_X behavior"). Under the current policy each draft ran three light gates, which put 113 CI runs in the queue ahead of beta.44's
publishjob and the release-please refresh. I cancelled those runs by hand (queue 116 → 3).Drafts now run no job:
scope-gate,gates, andbenchmark-harnesscarry the sameif(push, or non-draft, orci-full), and every guarded job already keys off scope-gate's outputs, so a skipped scope-gate skips the run without consuming a runner.plugin-validationandsdk-conformancealready skip drafts at job level.CONTRIBUTING.mdupdated.actionlint,tests/release_safety_test.sh,scripts/check-rust-cache-lineage.pypass.