ci: add CodeRabbit config (Gemini-sunset replacement reviewer) - #176
Conversation
CodeRabbit becomes the workhorse code reviewer as consumer Gemini Code Assist ceases 2026-07-17. CodeQL still owns security scanning (non-overlapping). .coderabbit.yaml ports the IEP review priorities into path_instructions — the failure classes DR-085 + the qualified-reviewer glance proved deterministic CI can't catch (3-way schema/Zod/ Pydantic drift, cross-artifact semantic drift, unenforced signed-row invariants, non-tamper-evident lineage, claims-vs-code, non-additive shape changes). Requires the CodeRabbit GitHub App installed on the account/org to take effect.
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request introduces CodeRabbit as the new automated review tool to ensure continued coverage following the sunset of Gemini Code Assist. The configuration is tailored to enforce strict validation rules for the Intent Eval Platform, focusing on schema parity, semantic consistency, and script safety. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
|
Warning Review limit reached
More reviews will be available in 35 minutes and 27 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?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 credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. 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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ✨ 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 |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces a .coderabbit.yaml configuration file to set up automated CodeRabbit reviews with specific path instructions. The reviewer correctly identified that the path glob configured for the kernel review instructions does not match the repository's directory structure (which uses specs/ and research/ instead of schemas/, src/, and python/), meaning the rules would not be applied. A suggestion was provided to update the path glob to include the correct directories.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| - "!pnpm-lock.yaml" | ||
| - "!**/*.lock" | ||
| path_instructions: | ||
| - path: "**/{schemas,src,python}/**" |
There was a problem hiding this comment.
The path glob **/{schemas,src,python}/** does not match the directory structure of the intent-eval-lab repository. In this repository, schemas are located under specs/ and Python scripts/tests are located under research/phase-a-0-baseline/.\n\nAs a result, CodeRabbit will silently skip applying these crucial kernel review instructions to the actual schema and Python files in this codebase.\n\nTo ensure these instructions are applied correctly, the path glob should be updated to include specs and research directories.
- path: "**/{schemas,src,python,specs,research}/**"References
- The repository style guide mandates strict checks for three-way schema drift and cross-artifact semantic consistency. The CodeRabbit configuration must be correctly scoped to the directories containing these files (such as specs/ and research/) to enforce these rules. (link)
1 participant
Adds
.coderabbit.yaml— CodeRabbit as the workhorse reviewer replacing Gemini Code Assist (consumer Gemini review ceases 2026-07-17). CodeQL still owns security (non-overlapping). The config'spath_instructionscarry the IEP failure-class checklist (3-way schema↔Zod↔Pydantic drift in both directions, cross-artifact semantic drift, unenforced signed-row invariants, non-tamper-evident lineage, claims-vs-code, non-additive shape changes) — the classes DR-085 + the glance + Gemini itself caught that deterministic CI can't. Requires the CodeRabbit GitHub App installed on the account/org to take effect.