[luv-68] fix: require-pr-before-stop skips when no changes vs base branch#67
Conversation
…anch
The policy was incorrectly denying stop when a PR was merged but no new
changes existed on the branch. Now checks git log + git diff against
origin/{baseBranch} before requiring a PR. Handles both regular and
squash merges. Adds configurable baseBranch param (default: "main").
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
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 23 minutes and 19 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: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ 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 |
Summary
require-pr-before-stoppolicy incorrectly firing when a PR was already merged and no new changes existed on the branchgit logfor commit ancestry (handles regular merges) +git diff --statfallback (handles squash merges)baseBranchparam (default:"main") so users can compare against a different base branchTest plan
bun run test:run)bun run build)🤖 Generated with Claude Code