mergify: add auto-rebase and conflict notification rules#1058
Conversation
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 52 minutes and 59 seconds. ⌛ 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. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis PR introduces two new Mergify automation rules to Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 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 |
There was a problem hiding this comment.
🧹 Nitpick comments (1)
.mergify.yml (1)
93-95: Consider scoping conflict notifications tomainonly.This avoids comment noise if the repo later introduces release/support branches.
Suggested diff
- name: Ping author on conflicts conditions: - "conflict" - "-closed" + - "base=main"🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.mergify.yml around lines 93 - 95, The current mergify rule triggers on any branch conflict; scope these notifications to the main branch by adding a base=main condition to the conditions list so the rule only matches when the PR target is main (adjust the conditions array that contains "conflict" and "-closed" to include "base=main" alongside them).
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In @.mergify.yml:
- Around line 93-95: The current mergify rule triggers on any branch conflict;
scope these notifications to the main branch by adding a base=main condition to
the conditions list so the rule only matches when the PR target is main (adjust
the conditions array that contains "conflict" and "-closed" to include
"base=main" alongside them).
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 469f18b2-cba4-4681-9af2-7d295d8b1de6
📒 Files selected for processing (1)
.mergify.yml
Add two new Mergify rules: - Auto-rebase approved PRs that are behind main, eliminating the need to manually comment "@mergify rebase" - Notify PR authors when merge conflicts are detected Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Lalatendu Mohanty <lmohanty@redhat.com>
75b28f8 to
2b32364
Compare
Add two new Mergify rules: