security(operations): retain private-reporting setting evidence - #423
Conversation
|
Warning Review limit reached
Next review available in: 56 minutes Limit details: You’ve used all 1 included review currently available under your plan. 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 (6)
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 |
…e) into current main origin/main's history was rewritten (new root ab3ebde at PR #450); this PR's original base commit a779375 (#423-era) and its one commit 7d95ca2 predate that rewrite and share no ancestor with current main, so a normal merge is refused ("refusing to merge unrelated histories"). This records the old branch tip as merged history (satisfying "merge base into head", not a rebase, and not a force-push) while keeping the tree from the preceding commit, which already carries the old branch's content reapplied onto current main by hand (README.md patch applied verbatim since it was byte-identical at the old base; docs/internal/README.md copied from the old head; CHANGELOG.md bullet updated to the old head's wording).
1 participant
Summary
Adds a repository-owned read-only operational evidence path for issue #73 so protected source can periodically prove the GitHub private-vulnerability-reporting setting without conflating that setting with reporter UI, notifications, staffing, case access, or end-to-end disclosure exercise evidence.
TDD state
RED-only head
ef3740763dad08253c139081f27abe798d4d6fdbadds an executable workflow contract requiring:artifacts/security/private-vulnerability-reporting-audit.jsonevidence for 30 days.Protected main has the audit implementation but no such workflow/package-script surface, so this contract is intentionally unsatisfied before the implementation mutation.
No central
.github, naruon, contextual-orchestrator, App configuration, live reporter UI, or other dedicated-writer repository is modified. The PR remains Draft until the GREEN implementation and fresh exact-head application/reviewer/Security evidence are terminal.