Repository navigation
Conversation
Fleet-wide PR-review outage: pr-review-trigger.yml passes lsp_pilot_variant to pr-review.yml@pr-review/next, but that channel-pinned reusable (last updated 2026-06-21) does not declare the input. Passing an undeclared input to a reusable is a workflow-file validation error, so EVERY review dispatch startup_failed (repository_dispatch / workflow_dispatch / check_suite) since the #1031/#1034 caller change landed (~03:16 UTC) — no PR could be reviewed. Remove only the with: forwarding line to restore reviews immediately. The workflow_dispatch input definition is retained (harmless, unused). Re-add the forwarding once the input is promoted to the pr-review/next reusable (then the #1031 LSP-pilot A/B leg works end-to-end). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HUhVsBbihbTjVvbcVf1WuU
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
|
Warning Review limit reached
Next review available in: 27 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 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.
Pull request overview
Restores the fleet’s PR-review trigger workflow by removing forwarding of an undeclared input (lsp_pilot_variant) to the channel-pinned reusable (pr-review.yml@pr-review/next), which was causing workflow validation failures and startup_failure on every dispatch.
Changes:
- Removed
lsp_pilot_variantfrom thewith:inputs passed to the pinned reusable to avoid “undeclared input” validation errors. - Left the
workflow_dispatchinput definition in place (documented as currently unused) so it can be re-enabled once the reusable declares the input.
Dev-Lead — review-changes (applied)Changes committed and pushed. |
|
Dev-Lead — review-changes (no-changes)No changes were needed for this PR. |
|
Closing per maintainer decision to take a different fix path (not admin-merging a revert). Root cause + the 1-line fix are documented here for reference if needed. The review-pipeline outage (pr-review-trigger.yml forwarding lsp_pilot_variant to the pr-review/next reusable that doesn't declare it) is still open. |



Fleet-wide PR-review outage — root cause + fix
Symptom: every PR-review dispatch has
startup_failured since ~03:16 UTC today; no PR can get a code-owner (donpetry-bot) review. Only thePR Review Agent — Triggerworkflow is affected (all other workflows healthy).Root cause: #1031/#1034 (
a492721ad) addedlsp_pilot_variant: ${{ inputs.lsp_pilot_variant || '' }}to thewith:block that callspr-review.yml@pr-review/next. That channel-pinned reusable (last updated 2026-06-21) does not declare that input — passing an undeclared input to a reusable is a workflow-file validation error → startup_failure on every dispatch (repository_dispatch / workflow_dispatch / check_suite). Caller-vs-channel skew.Fix: remove only the forwarding line. The
workflow_dispatchinput definition is retained (validtype: choice, harmless while unused). Re-add the forwarding once the input is promoted to thepr-review/nextreusable (then #1031's LSP-pilot A/B leg works end-to-end).This restores the review pipeline, but merging it requires the very review gate it fixes — so it needs an admin-merge / direct authorization to break the cycle. CI on this PR should be green; the code-owner review will keep failing until this lands.
🤖 Generated with Claude Code