feat: implement issue #348 — Compliance: stub-surface-drift-pr-auto-review.yml-concurrency - #373
feat: implement issue #348 — Compliance: stub-surface-drift-pr-auto-review.yml-concurrency#373don-petry wants to merge 3 commits into
Conversation
…eview.yml-concurrency
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Review limit reached
Next review available in: 43 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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Code Review
This pull request updates the pr-auto-review-workflow.bats test suite to assert that the pr-auto-review workflow stub does not declare a top-level concurrency block, aligning with its central management. Feedback was provided to use safe navigation when loading the YAML file (e.g., yaml.safe_load(...) or {}) to prevent potential TypeError exceptions if the file is empty.
Dev-Lead — review-changes (applied)Changes committed and pushed. |
There was a problem hiding this comment.
Pull request overview
Aligns the repository’s pr-auto-review.yml caller stub with the centrally owned workflow surface to resolve compliance finding #348 (stub-surface drift on concurrency). This fits the codebase’s pattern of using thin caller stubs that must mirror org standards verbatim for on:, permissions:, and centrally owned workflow attributes.
Changes:
- Removed the locally defined top-level
concurrency:block from.github/workflows/pr-auto-review.ymlto eliminate drift from the canonical org template. - Updated the Bats workflow guard to assert that the caller stub does not declare a top-level
concurrency:block, reflecting the centrally owned surface.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
scripts/tests/pr-auto-review-workflow.bats |
Updates the guardrails to enforce “no top-level concurrency” on the thin caller stub per compliance check #348. |
.github/workflows/pr-auto-review.yml |
Removes the repo-local top-level concurrency: block to re-sync the stub with the org standard template surface. |
|
Fixed in scripts/tests/pr-auto-review-workflow.bats line 25: added safe YAML load fallback ( |
Dev-Lead — fix-bot-comment (applied)Changes committed and pushed. |
|
|
Auto-rebase failed — merge conflict — this branch has conflicts with dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention. To resolve manually instead: |
|
Auto-rebase failed — merge conflict — this branch has conflicts with dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention. To resolve manually instead: |



Closes #348
Implemented by dev-lead agent. Please review.