Conversation
|
Warning Review limit reached
More reviews will be available in 51 minutes and 40 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. 📝 WalkthroughWalkthroughAdds a new v7.6.0 release section to Changesv7.6.0 Release Publication
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 1✅ Passed checks (1 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.
Actionable comments posted: 4
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
src/pages/roadmap.astro (1)
305-305:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winResolve inconsistency between years metric and descriptive text.
The header stat (line 183) shows "Years Journey" as 6, but the journey stat text (line 305) says "5.5 years of continuous evolution." These values should be aligned. Verify which is the correct figure and update accordingly.
📊 Options to resolve
Option 1: Update the header stat to match the text:
- <div class="text-4xl font-bold text-primary">6</div> + <div class="text-4xl font-bold text-primary">5.5</div>Option 2: Update the text to match the header stat:
- From Laravel backend to Vue3 frontend to FrankenPHP — 5.5 years of continuous evolution + From Laravel backend to Vue3 frontend to FrankenPHP — 6 years of continuous evolutionAlso applies to: 305-305
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: a5de2133-bd95-4369-adce-cc1f56865afb
📒 Files selected for processing (3)
docs/releases.mdsrc/components/widgets/Announcement.astrosrc/pages/roadmap.astro
Summary by CodeRabbit