ci(release-nightly): centralize FORCE_RELEASE logic in check_changes job#789
Conversation
nicholas-fedor
commented
May 1, 2026
- move FORCE_RELEASE condition from job-level to individual steps
- handle force release within check_changes step instead of downstream jobs
- simplify test and build job conditions by removing redundant FORCE_RELEASE checks
- move FORCE_RELEASE condition from job-level to individual steps - handle force release within check_changes step instead of downstream jobs - simplify test and build job conditions by removing redundant FORCE_RELEASE checks
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ 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: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
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. Review rate limit: 0/1 reviews remaining, refill in 34 minutes and 17 seconds.Comment |
Up to standards ✅🟢 Issues
|