feat: cap reviewer concurrency at 2 uniformly across providers - #5
Conversation
Reviews ran effectively sequentially: opencode declared maxConcurrentReviews: 1 and appears in nearly every pipeline, so effectiveConcurrencyLimit (which takes the global min) pinned the whole pipeline to 1 concurrent reviewer. - Raise opencode/opencode-go maxConcurrentReviews 1 -> 2 - Add maxConcurrency to defaults schema and propagate it to pipelines that don't set their own (pipeline-level value still wins) Net effect: every pipeline runs at most 2 reviewers simultaneously, uniform across all providers. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
📝 WalkthroughWalkthroughAdds an optional ChangesConcurrency configuration changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
✨ Finishing Touches📝 Generate docstrings
🧪 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 |
🧭 Quorum ReviewQuorum requires an
Add |
Reviews ran effectively sequentially: opencode declared maxConcurrentReviews: 1 and appears in nearly every pipeline, so effectiveConcurrencyLimit (which takes the global min) pinned the whole pipeline to 1 concurrent reviewer.
Net effect: every pipeline runs at most 2 reviewers simultaneously, uniform across all providers.
Summary by CodeRabbit
New Features
Tests