chore: exclude proto dir from coderabbit reviews by whoAbhishekSah · Pull Request #1473 · raystack/frontier
Warning
Rate limit exceeded
@whoAbhishekSah has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 24 minutes and 21 seconds before requesting another review.
⌛ How to resolve this issue?
After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.
We recommend that you space out your commits to avoid hitting the rate limit.
🚦 How do rate limits work?
CodeRabbit enforces hourly rate limits for each developer per organization.
Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.
Please see our FAQ for further information.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 728b0bf9-fc45-4afd-a3eb-76136d353733
📒 Files selected for processing (1)
.coderabbit.yaml
📝 Walkthrough
Walkthrough
Added path filter configuration to .coderabbit.yaml to exclude the proto/ directory from code review processing. The change introduces a single filter pattern !proto/** under the reviews.path_filters setting.
Changes
| Cohort / File(s) | Summary |
|---|---|
Configuration Update .coderabbit.yaml |
Added reviews.path_filters: ["!proto/**"] to exclude proto paths from review processing. |
Estimated code review effort
🎯 1 (Trivial) | ⏱️ ~3 minutes
Suggested reviewers
- rohilsurana
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 @coderabbitai help to get the list of available commands and usage tips.