doc/readme#57
Conversation
|
Warning Review limit reached
More reviews will be available in 44 minutes and 19 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. 📝 WalkthroughWalkthroughThe ChangesAllesLocker README Overhaul
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@README.md`:
- Line 4: The README contains a branding inconsistency where the h1 heading uses
"AllesLocker" (single word) while the description on line 6 uses "Alles Locker"
(two words). Choose one consistent branding format and apply it throughout the
entire README file. Update either the h1 heading element that currently contains
"AllesLocker" or the description text on line 6 to match the chosen branding
convention, ensuring all references to the product name follow the same format.
- Line 2: The README has two issues to fix. First, update the repository links
on lines 33-34 that reference `alleslockr` (lowercase) to use the correct
organization name `AllesLockr` (with capital L and R) to match the wiki link on
line 29. Second, move the external images currently referenced from
`media.nocars.tk/` on lines 2 and 9 into the repository directory and update
those image source paths to use relative file paths (e.g., `./images/lock.svg`)
instead of the external CDN URLs to eliminate external dependencies and ensure
long-term reliability.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
2 participants
Summary by CodeRabbit