Remove codename from documentation#6
Conversation
Co-authored-by: Ben Schellenberger <bschellenberger2600@users.noreply.github.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 38 minutes and 14 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 (3)
✨ 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 |
This change removes all references to the internal
git-fcukcodename from project documentation. The README section on rewrite orchestration now uses a neutral heading.SPEC.mdandCURSOR_ULTRA_PLAN.mdrefer to a generic companion history CLI where a second consumer was previously named, avoiding an unreleased or non-public name.Tests:
go test -count=1 ./...