[webhooks] batching support - #216
Conversation
|
Warning Review limit reached
Next review available in: 55 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. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe documentation replaces the inbox export endpoint with inbox refresh and documents individual, batch, and disabled webhook delivery. It also adds batch webhook event types, ordering, payload limits, usage guidance, and an example payload. ChangesInbox Refresh Webhooks
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
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 `@docs/features/reading-messages.md`:
- Around line 83-87: Update the API Endpoints table and endpoint count in the
documentation to replace POST /messages/inbox/export and its anchor with POST
/3rdparty/v1/inbox/refresh, matching the documented section heading and ensuring
users are directed to the replacement route.
In `@docs/features/webhooks.md`:
- Around line 78-85: Update the batch webhook documentation for
mms:batch:downloaded by documenting or linking its individual mms:downloaded
event schema as the payload source; if that individual event is unsupported,
remove mms:batch:downloaded from the available batch events list.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 854fa452-cc79-4e51-83cb-017e6a23fc15
📒 Files selected for processing (2)
docs/features/reading-messages.mddocs/features/webhooks.md
Deploying docs with
|
| Latest commit: |
6683744
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://68e0569d.docs-7wm.pages.dev |
| Branch Preview URL: | https://features-batch-webhooks.docs-7wm.pages.dev |
1a2d1b8 to
6683744
Compare
Summary by CodeRabbit