Configure coderabbit not to apply conflicting labels#714
Configure coderabbit not to apply conflicting labels#714rapids-bot[bot] merged 2 commits intoNVIDIA:developfrom
Conversation
… on a PR Signed-off-by: David Gardner <dagardner@nvidia.com>
|
Warning Rate limit exceeded@dagardner-nv has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 8 minutes and 31 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the 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. 📒 Files selected for processing (1)
WalkthroughThe PR updates .coderabbit.yaml label instructions to enforce mutual exclusivity. It adds explicit “do not apply if already present” checks for the breaking/non-breaking pair and for the bug/doc/feature request/improvement group. No other label blocks are changed. Changes
Sequence Diagram(s)sequenceDiagram
autonumber
participant PR as PR
participant Bot as Labeler Bot (.coderabbit.yaml rules)
participant GH as GitHub Labels
rect rgba(225,245,254,0.6)
note over Bot: Apply breaking/non-breaking labels
PR->>Bot: Request label: breaking or non-breaking
Bot->>GH: Check existing labels (breaking/non-breaking)
alt existing in {breaking, non-breaking}
Bot-->>PR: Do not apply label
else no conflicting label
Bot->>GH: Apply requested label
GH-->>PR: Label applied
end
end
rect rgba(232,245,233,0.6)
note over Bot: Apply bug/doc/feature request/improvement labels
PR->>Bot: Request label: bug/doc/feature request/improvement
Bot->>GH: Check existing labels in group
alt existing in {bug, doc, feature request, improvement}
Bot-->>PR: Do not apply label
else no conflicting label
Bot->>GH: Apply requested label
GH-->>PR: Label applied
end
end
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested labels
✨ Finishing Touches🧪 Generate unit tests
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
Status, Documentation and Community
|
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (5)
.coderabbit.yaml (5)
129-131: Tighten phrasing and fix minor grammar for multi-category exclusivityUse “any of … labels” (plural) for clarity with 4-way exclusivity and add a missing comma after “apply this label”. This keeps instructions concise and LLM-friendly without changing intent.
Apply this diff:
- apply this label do not apply the "doc", "feature request", or "improvement" labels. If the PR already has - either the "bug", "doc", "feature request", or "improvement" label, do not apply this label. + apply this label, do not apply the "doc", "feature request", or "improvement" labels. If the PR already has + any of the "bug", "doc", "feature request", or "improvement" labels, do not apply this label.
139-141: Normalize spacing and wording; remove double space and pluralize “labels”Same suggestion as for “bug”; also remove the double space before “If the PR…”.
Apply this diff:
- apply this label do not apply the "bug", "feature request", or "improvement" labels. If the PR already has - either the "bug", "doc", "feature request", or "improvement" label, do not apply this label. + apply this label, do not apply the "bug", "feature request", or "improvement" labels. If the PR already has + any of the "bug", "doc", "feature request", or "improvement" labels, do not apply this label.
152-154: Consistent exclusivity phrasing across the 4-way groupAlign wording with the other entries for consistency and readability.
Apply this diff:
- to the toolkit. If you apply this label do not apply the "bug", "doc", or "improvement" labels. If the PR - already has either the "bug", "doc", "feature request", or "improvement" label, do not apply this label. + to the toolkit. If you apply this label, do not apply the "bug", "doc", or "improvement" labels. If the PR + already has any of the "bug", "doc", "feature request", or "improvement" labels, do not apply this label.
158-159: Fix punctuation and pluralization; remove double spaceKeep copy uniform with the other mutually exclusive labels.
Apply this diff:
- the "bug", "doc", or "feature request" labels. If the PR already has either the "bug", "doc", - "feature request", or "improvement" label, do not apply this label. + the "bug", "doc", or "feature request" labels. If the PR already has any of the "bug", "doc", + "feature request", or "improvement" labels, do not apply this label.
168-169: Minor copy edit: remove double space and simplify label mentionsFor two-way exclusivity, “either … or …” is fine; also drop redundant trailing “label” and the extra space.
Apply this diff:
- apply the "breaking" label. If the PR already has either the "breaking" or "non-breaking" label, do not apply - this label. + apply the "breaking" label. If the PR already has either "breaking" or "non-breaking", do not apply this label.
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (1)
.coderabbit.yaml(4 hunks)
🔇 Additional comments (1)
.coderabbit.yaml (1)
121-126: Mutual exclusivity for breaking/non-breaking — LGTMThe added guard against re-applying or cross-applying breaking vs non-breaking matches the PR objective and should reduce label flip-flops when auto-apply is enabled.
Signed-off-by: David Gardner <dagardner@nvidia.com>
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
|
/merge |
2 participants
Description
By Submitting this PR I confirm:
Summary by CodeRabbit