Repository navigation
ci: Reduce shared Actions pool usage with concurrency cancellation and draft-skip - #302
Merged
Merged
Conversation
|
Claude review · advisory Reviewed Open: 0 blocking · 0 should-fix · 0 nit. ✅ Nothing blocking. Fix or reply to each thread; the next revision's review re-checks open threads and resolves those it agrees are handled. Resolving a thread yourself also closes it. Later revisions review only what changed. |
kavmur
force-pushed
the
ci/github-actions-hygiene
branch
from
October 9, 2026 22:16
e05aa16 to
6a3eae9
Compare
…d draft-skip Amazon's ubuntu-latest runners draw on one enterprise-wide shared concurrency pool that degrades silently under load. Apply the four org-recommended hygiene practices to this repo's PR-triggered CI workflows, matching the fix landed on aws-deadline/deadline-cloud. - Add a P2-correct concurrency block (group keyed on workflow+ref with a conditional suffix: a shared 'pr' group for pull_request events so superseded runs cancel, github.run_id otherwise to isolate non-PR events and avoid cancelling pending push/schedule/workflow_call runs). - code_quality: add draft-skip on the heavy Test matrix and make fail-fast explicit. - codeql, security_scan: concurrency only (required checks; not draft-gated so the merge queue does not stall). - record_pr, auto_approve: concurrency only (lightweight PR automations). Purely additive; no existing logic removed or rewritten. Signed-off-by: kavmur <kavmur@users.noreply.github.com>
kavmur
force-pushed
the
ci/github-actions-hygiene
branch
from
October 14, 2026 19:27
6a3eae9 to
2b2fba5
Compare
leongdl
approved these changes
Oct 27, 2026
leongdl
approved these changes
Oct 27, 2026
godobyte
approved these changes
Oct 27, 2026
AlexTranAmz
approved these changes
Oct 27, 2026
congr
approved these changes
Oct 27, 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
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.
What was the problem/requirement? (What/Why)
PR-triggered CI workflows had no
concurrencyblock, so superseded runs on a branch kept running and new pushes queued extra jobs on the shared enterpriseubuntu-latestpool. With agent-driven development pushing frequently per PR, this wastes runner capacity on a pool that degrades silently under load.What was the solution? (How)
Applied the org admins' recommended GitHub Actions hygiene practices to the PR CI workflows (
code_quality.yml, codeql.yml, security_scan.yml, record_pr.yml, auto_approve.yml), purely additive:pull_requestevents share a per-ref group so a new push supersedes the in-progress run; all other events (push/release/workflow_call) get a uniquegithub.run_idsuffix so they never cancel each other's pending runs.ready_for_reviewtrigger +if: github.event.pull_request.draft != true). Not applied tocodeql/security_scanso those keep reporting.fail-faston thecode_qualitymatrix.What is the impact of this change?
Lower consumption of the shared Actions runner pool, especially on draft PRs and rapid push bursts. No change to what the jobs do. Verified: not a required status check —
mainlineonly requiresSemantic PRandDCO, so skipping these jobs on drafts cannot stall the merge queue.How was this change tested?
Statically validated — every edited workflow parses cleanly with
yaml.safe_loadand the concurrency/if guards were confirmed structurally. Runtime behavior (cancel-on-push, draft-skip) manifests only on GitHub's runners; recommend opening as a draft first to confirm the heavy jobs skip, then marking ready.Integ test result
N/A — CI configuration only; no
src/changes.Installer test result
N/A — no
installer/orsrc/changes.Did you run the "Job Bundle Output Tests"? If not, why not? If so, paste the test results here.
N/A — change is limited to
.github/workflows/; no submitter or adaptor code touched.Was this change documented?
No doc changes needed — workflow-config only.
Did you modify schema files?
Is this a breaking change?
No. Draft-skip (Yes —
code_quality.yml's matrix build skips draft PRs and sets explicitfail-fast.) Additive workflow metadata only; no public contract or adaptor interface changed.