Repository navigation
chore(ci): add CodeRabbit review config - #9
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
@coderabbitai review |
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughAdds a ChangesReview configuration
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~4 minutes Change: Other Merge Risk: ⚪ Minimal · up to The configuration is mergeable after normal checks; no actionable issue was found. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
A bare include pattern turned the filter list into an allowlist, so CodeRabbit skipped every file except en.json. Locale JSON is generated by i18n:extract and covered by the i18n CI check, so exclude it all. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Description
Adds
.coderabbit.yamlso CodeRabbit reviews PRs intodevelop(andmain). It skips drafts, lockfiles,dist/, and non-English locale files, and it adds an extra check for migrations so SQLite and Postgres changes stay in step.developis now protected by a ruleset, so this is also the first PR under the new flow.How Has This Been Tested?
Config only. CodeRabbit will check it against its schema on the first review once the GitHub App is installed on the repo.
Checklist:
bun run buildbun run i18n:extract🤖 Generated with Claude Code
Summary by CodeRabbit
developandmainbranches, with draft changes and selected files excluded from review.