Sync Kaizen shared skills - #42
Conversation
|
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: 58 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: ASSERTIVE 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 |
|
@codex review |
|
@coderabbitai review |
✅ Action performedReview finished.
|
![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: f492b4c52d
ℹ️ 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".
| echo 'reviewThreads returned an invalid or incomplete response' >&2 | ||
| exit 1 | ||
| fi | ||
| page="$(gh "${args[@]}")" |
There was a problem hiding this comment.
With this unguarded command substitution (and the same pattern in the nested comment loop), an auth, rate-limit, or GraphQL failure leaves page empty or shaped like an error response; the following jq -r ...hasNextPage then yields an empty string/null, so the loop breaks and the guardian can report zero unresolved feedback instead of blocking as an incomplete audit. The repo requires the vendored PR guardian to keep running until a PR is truly mergeable, so this should fail closed and validate the response before continuing.
Useful? React with 👍 / 👎.
| gh api --paginate 'repos/<owner>/<repo>/commits/<head-sha>/check-runs?per_page=100' | ||
| gh api --paginate 'repos/<head-owner>/<head-repo>/commits/<head-sha>/check-runs?per_page=100' # when different | ||
| gh api --paginate 'repos/<check-run-owner>/<check-run-repo>/check-runs/<check-run-id>/annotations?per_page=100' | ||
| gh api --paginate 'repos/<owner>/<repo>/check-runs/<check-run-id>/annotations?per_page=100' |
There was a problem hiding this comment.
For fork PRs where checks are created in the head repository, hard-coding annotation fetches to <owner>/<repo> misses those runs or fetches annotations from the wrong repository; GitHub documents Checks API lookups as repository-scoped and notes they only look in the repository where the check suite or run was created (docs). The guardian can therefore report no actionable check annotations even though head-repo CI produced findings, so retain the head repository from the PR query and fetch annotations from the repository that returned each run.
Useful? React with 👍 / 👎.
2 participants
Summary
Verification
Generated by the shared-skill sync workflow.
Closes kaizen-agents-org/.github#153