chore: superseded by clean HMAC-readiness PR #313 - #333
Conversation
|
Warning Review limit reached
Next review available in: 8 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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)
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 |
Superseded duplicate
Closed in favor of PR #313.
Fresh comparison proves both branches are clean reconstructions from protected
main55d7ae8647208e301f282350f076eeddaba61d11and carry the same production blobaf989ab08a026418cf31fb7693316a65a84f77e2. Their tests differ only in the descriptive null-secret test method name; both exercise the same controlled missing-secret boundary.PR #313 exact head
610f081cc56cfcaa372d674a56f4b21c91123c8fis already Ready, mergeable, auto-merge enabled, and GREEN on CI31387412055, Security Scan31387411478, SAST31387411422, and fuzz31387412079. Keeping both PRs would duplicate writer ownership, checks, review requests, and merge risk without adding product behavior.This closure does not mark issue #319 complete. Runtime credential-registry migration remains separate from bounded HMAC readiness.