chore(review): pin revision-aware runtime on dev - #307
Conversation
|
Warning Review limit reached
Next review available in: 5 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 Plus 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 |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7b5c6b86b8
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| secrets: | ||
| CODEX_AUTH_JSON: ${{ secrets.REVIEWROUTER_CODEX_AUTH_JSON }} |
There was a problem hiding this comment.
With the new T0 reusable workflow, the pinned runtime loads ReviewLedger from secrets.REVIEW_ROUTER_LEDGER_KEY before building the lifecycle inventory and treats a missing key as review_action_v2_command_ledger_unavailable; this caller only forwards CODEX_AUTH_JSON, so every dispatched Codex review in this workflow will run with an empty ledger key and fail before publishing results. Please pass REVIEW_ROUTER_LEDGER_KEY: ${{ secrets.REVIEW_ROUTER_LEDGER_KEY }} here, matching the interaction workflow that writes the ledger.
Useful? React with 👍 / 👎.
1 participant
Pins the managed ReviewRouter review and interaction workflows on dev to the same immutable revision-aware Action release already merged on main. This is required for draft PRs targeting dev, including #252, to use the durable workflow-dispatch path instead of the legacy pull_request workflow.
Greptile Summary
Pins ReviewRouter workflows to an immutable revision-aware runtime.
Confidence Score: 5/5
The PR appears safe to merge with no concrete changed-code failure identified.
The review and interaction workflows consistently use the same immutable runtime revision, and the new dispatch conditions cleanly separate identity-bearing reviews from scheduled or input-free maintenance runs.
Important Files Changed
Reviews (1): Last reviewed commit: "chore(review): pin revision-aware runtim..." | Re-trigger Greptile