Repository navigation
docs: refresh README for multi-account launch - #9
Conversation
|
Warning Review limit reached
Next review available in: 50 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?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 reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. 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, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. 📝 WalkthroughWalkthroughREADME documentation is updated for the security model, local and production setup, mailbox-profile onboarding, provider scopes, audit-log access, project structure, and shipped roadmap capabilities. ChangesREADME documentation updates
Estimated code review effort: 1 (Trivial) | ~5 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
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`:
- Around line 489-492: Update the README project-tree listing near the docs
entries to include credential-handoff.md and mailbox-cleanup.md with
descriptions matching their linked documentation, or explicitly mark the tree as
intentionally abbreviated; keep the documented tree consistent with the README
links.
- Line 233: Update the README configuration example around the mailboxAccess
setting to default to send-only Outlook access by removing or disabling
mailboxAccess and its named mailbox profile from the basic example. Add a
separate named-profile snippet that explicitly enables mailboxAccess and retains
the required profile configuration, while preserving the existing scope
guidance.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
|
Addressed both CodeRabbit findings in
Revalidated both YAML examples, all Markdown fences, repository-relative links, and |
Summary
Mail.ReadWrite, named profile configuration, and Gmail--profileonboardingVerification
npm test— 142/142 passed on the unchanged code at this branch basegit diff --checkpersonalandworkprofile mappings.github/workflows/ci.ymlexists and is activeREADME.mdchangedScope
Documentation only. No runtime, configuration, credential, deployment, or mailbox changes.
Summary by CodeRabbit