docs: update executor note to reflect always-included interceptor#78
docs: update executor note to reflect always-included interceptor#78
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 46 minutes and 57 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. ✨ 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.
Pull request overview
Clarifies the integrations documentation around per-call WithExecutor support by updating the note to reflect that the default client interceptor set already includes the required executor interceptor.
Changes:
- Updated the “Per-call executor” info note to state that
DefaultClientInterceptorsalways includesExecutorClientInterceptor.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Summary
DefaultClientInterceptorsalways includesExecutorClientInterceptor, so per-callWithExecutorworks out of the boxTest plan
Companion to go-coldbrew/interceptors#53.