Conversation
|
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 13 minutes and 10 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 (24)
✨ 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 |
|
bugbot run |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit fc762b7. Configure here.
Summary
This PR does two related cleanup passes across the community integrations repo:
nmemas the universal fallbackIt also syncs the nested Gemini CLI integration to the latest needed submodule commit.
What changed
docs/USER_OVERRIDE_GUIDE.mddocs/PLUGIN_DEVELOPMENT_GUIDE.mdand the repo README with that policyplugin + MCPsetup0.1.5integrations.jsonso Codex is described ascli+mcpnowledge-mem-gemini-clisubmodule pointerWhy
We were telling users not to edit installed plugin files, but that guidance mostly lived in contributor docs or scattered package READMEs. The policy needs to be explicit and consistent:
plugin + MCPgives better initiative and tool useNotes
save-thread