Repository navigation
CI: 878 Actions runs queued, required checks on new PRs never start #7483
Description
Measured 2026-10-07 ~11:00 UTC via the REST API:
actions/runs?status=queued: 878 runsactions/runs?status=in_progress: 16 runs- the three most recently completed runs (Documented Commands, Withdrawn Number Gate, Conflict Markers) all ended
cancelled
Effect: required checks (check-linked-issue, own-language, parse-ratchet, validate) on fresh PRs stay queued for 20+ minutes, e.g. #7477 and #7454, so no PR can merge under the ruleset.
Likely shape (not yet proven): every push to every open PR queues the full workflow set, and runner concurrency (~16) drains far slower than bees push. Options to evaluate:
concurrency: { group: ${{ github.workflow }}-${{ github.head_ref || github.ref }}, cancel-in-progress: true }on PR workflows that lack it, so a re-push drops the stale run instead of queueing behind it.paths:filters so spec-only PRs skip Rust/CI-only workflows.- Run the four required checks first (separate light workflow) so merges are not blocked behind heavy optional suites.
Done when a fresh PR's required checks start within a few minutes and the queued count stays bounded.
Activity
gHashTag commentedon Oct 7, 2026
Reopened 2026-10-07: the bulk close of issues without a
## Boundarysection was reverted by the owner. Nothing to do here; this comment replaces the earlier close notice.tri-claw commentedon Oct 8, 2026
The Queen cannot take this issue yet. A bee starts only on an issue whose body has every section below, and this one lacks:
- specs/x.t27); without it the Queen reserves nothing and no bee can take the issueFR-001: ... MUST ...exit 0, or a backticked commandShe tried to write them 2 times and could not (last: not a task: This issue is about GitHub Actions CI configuration (workflow concurrency, paths filters, required checks) rather than t27 language specifications (.t27 files). No candidate paths exist in the reposit). Add them and the next round takes it. The rule is
specs/policy/issue_shape.t27.