fix(ci): run PR workflows when a draft is marked ready for review#488
Conversation
Both code-pull-request.yml and dco.yml gate their jobs on github.event.pull_request.draft == false, but the pull_request trigger omitted the ready_for_review event type. A PR opened as draft therefore got a run with every job skipped (and the Validate Code fan-in gate reported failure), and marking the PR ready never triggered a fresh run, leaving the PR stuck with a spurious failed check until an unrelated push. Adding ready_for_review to the trigger types makes both workflows re-run when a draft is promoted. Signed-off-by: Rhuan Barreto <rhuan@barreto.work>
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_64a648ae-ba69-4387-99e1-d46b964ae715) |
|
Warning Review limit reached
Next review available in: 57 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 (2)
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 |
Deploying archgate-cli with
|
| Latest commit: |
9a8423e
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://43827a6e.archgate-cli.pages.dev |
| Branch Preview URL: | https://fix-ci-ready-for-review.archgate-cli.pages.dev |
Code Coverage
Full HTML report available in workflow artifacts. Per-directory breakdown
|
|
@coderabbitai approve |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
✅ Action performedComments resolved and changes approved. |
# archgate ## [0.50.0](v0.49.0...v0.50.0) (2026-07-17) ### Features * **engine:** cache ctx.ast() parse results within a single check run ([#487](#487)) ([40b39d3](40b39d3)), closes [#482](#482) * **engine:** ctx.findAstNodes() generic AST node collector ([#486](#486)) ([f14b73b](f14b73b)), closes [#483](#483) * **engine:** support { comments: true } for ctx.ast() Ruby ([#485](#485)) ([36b891f](36b891f)), closes [#484](#484) ### Bug Fixes * **ci:** run PR workflows when a draft is marked ready for review ([#488](#488)) ([ab1fc96](ab1fc96)), closes [#485](#485) [#486](#486) --- This PR was generated with [simple-release](https://github.com/TrigenSoftware/simple-release). <details> <summary>📄 Cheatsheet</summary> <br> You can configure the bot's behavior through a pull request comment using the `!simple-release/set-options` command. ### Command Format ````md !simple-release/set-options ```json { "bump": {}, "publish": {} } ``` ```` ### Useful Parameters #### Bump | Parameter | Type | Description | |-----------|------|-------------| | `version` | `string` | Force set specific version | | `as` | `'major' \| 'minor' \| 'patch' \| 'prerelease'` | Release type | | `prerelease` | `string` | Pre-release identifier (e.g., "alpha", "beta") | | `firstRelease` | `boolean` | Whether this is the first release | | `skip` | `boolean` | Skip version bump | | `byProject` | `Record<string, object>` | Per-project bump options for monorepos | #### Publish | Parameter | Type | Description | |-----------|------|-------------| | `skip` | `boolean` | Skip publishing | | `access` | `'public' \| 'restricted'` | Package access level | | `tag` | `string` | Tag for npm publication | ### Usage Examples #### Force specific version ````md !simple-release/set-options ```json { "bump": { "version": "2.0.0" } } ``` ```` #### Force major bump ````md !simple-release/set-options ```json { "bump": { "as": "major" } } ``` ```` #### Create alpha pre-release ````md !simple-release/set-options ```json { "bump": { "prerelease": "alpha" } } ``` ```` #### Publish with specific access and tag ````md !simple-release/set-options ```json { "bump": { "prerelease": "beta" }, "publish": { "access": "public", "tag": "beta" } } ``` ```` ### Access Restrictions The command can only be used by users with permissions: - repository owner - organization member - collaborator ### Notes - The last comment with `!simple-release/set-options` command takes priority - JSON must be valid, otherwise the command will be ignored - Parameters apply only to the current release execution - The command can be updated by editing the comment or adding a new one </details> <!-- Please do not edit this comment. simple-release-pull-request: true simple-release-branch-from: release simple-release-branch-to: main --> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
1 participant
Problem
code-pull-request.ymlanddco.ymlgate every job ongithub.event.pull_request.draft == false, but theirpull_requesttriggers only listed[opened, edited, synchronize, reopened]. A PR opened as draft therefore got a run where every job was skipped — which made the "Validate Code" fan-in gate report failure — and marking the PR ready for review never triggered a fresh run, sinceready_for_reviewwas not in the trigger list. The PR stayed stuck with a spurious failed/skipped check until an unrelated push. This surfaced on #485, #486, and #487.Fix
Add
ready_for_reviewto thepull_requesttriggertypesin both workflows, so promoting a draft to ready triggers a run whose jobs actually execute. Two-line diff, nothing else changed.Validation
bun run validatepasses (lint, typecheck, format:check, 1558 tests, ADR check, knip, build check)bun run cli checkclean: 44/44 rules pass, 0 warnings