ci(was): ref-scoped concurrency retrofit#18
Conversation
Intent: prevent runaway CI fan-out by giving each per-commit/scheduled workflow a ref-scoped concurrency group (github.ref => merge-queue-safe, no #852 self-eviction). Additive only.
|
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_2bd18c5a-9987-490f-8430-73c4df354f70) |
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 45 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Risk: low. Cursor Bugbot did not complete successfully (check skipped due to usage limit), so the required automated review signal is unavailable. Human review is needed before merge; no reviewers were assigned.
Sent by Cursor Approval Agent: Pull Request Router and Approver
![wave-av-reviewbot[bot]](https://avatars.githubusercontent.com/u/211066493?s=60&v=4){kind=small}
1 participant
Adds a ref-scoped
concurrency:block to per-commit/scheduled workflows lacking one (WAS Phase 3 retrofit).Group
${{ github.workflow }}-${{ github.ref }}is merge-queue-safe (queue runs on a different ref, so no #852 self-eviction). Reusables + release workflows exempt.Files:
foundation-gate.ymlNote
Low Risk
CI-only workflow metadata change; no application code or secrets handling.
Overview
Adds a ref-scoped
concurrencyblock tofoundation-gate.ymlso only the latest run per branch/ref is kept and older in-flight runs are cancelled (cancel-in-progress: true).The group is
${{ github.workflow }}-${{ github.ref }}, matching the WAS Phase 3 retrofit used elsewhere (e.g.public-repo-guard,python-lint) and staying merge-queue-safe because queue runs use a different ref than the PR branch.Reviewed by Cursor Bugbot for commit 5bd3fa3. Configure here.
Summary by cubic
Add a ref-scoped concurrency block to
foundation-gate.ymlto prevent duplicate runs on the same ref and reduce CI fan-out. Uses group${{ github.workflow }}-${{ github.ref }}withcancel-in-progress: true, which is merge-queue safe.Written for commit 5bd3fa3. Summary will update on new commits.