security: add same-repo PR guard (P1 — fork PR protection)#85
security: add same-repo PR guard (P1 — fork PR protection)#85hummbl-dev wants to merge 3 commits into
Conversation
P1 mitigation from runner fleet wargame (2026-07-23). Adds `if: github.event_name != 'pull_request' || github.event.pull_request.head.repo.full_name == github.repository` to 2 job(s) running on self-hosted runners. This blocks fork PRs from triggering CI on persistent self-hosted runners while preserving CI for same-repo branches. Fork PRs will rely on post-merge validation (push to main) instead.
P1 mitigation from runner fleet wargame (2026-07-23). Adds `if: github.event_name != 'pull_request' || github.event.pull_request.head.repo.full_name == github.repository` to 1 job(s) running on self-hosted runners. This blocks fork PRs from triggering CI on persistent self-hosted runners while preserving CI for same-repo branches. Fork PRs will rely on post-merge validation (push to main) instead.
P1 mitigation from runner fleet wargame (2026-07-23). Adds `if: github.event_name != 'pull_request' || github.event.pull_request.head.repo.full_name == github.repository` to 1 job(s) running on self-hosted runners. This blocks fork PRs from triggering CI on persistent self-hosted runners while preserving CI for same-repo branches. Fork PRs will rely on post-merge validation (push to main) instead.
|
Warning Review limit reached
Next review available in: 42 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: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
✨ 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 |
1 participant
Summary
P1 mitigation from the runner fleet wargame (2026-07-23). Prevents fork PR code execution on persistent self-hosted runners.
Changes
Added a same-repo PR guard to 4 job(s) across 3 workflow(s):
How it works
push: [main]) validates the merged code.Why
The original wargame plan was to move PR-triggered workflows to
ubuntu-latest(GitHub-hosted runners). This was blocked by the operator constraint: no GitHub-hosted Actions minutes. The same-repo guard achieves the same security goal — preventing external attackers from running code on persistent self-hosted runners — without using any hosted minutes.Operator notes
push: [main]) will validate all merged code, including fork PRs.See
_internal/wargame/runner-fleet_2026-07-23/p1-redesign-matrix.mdfor the full design document.Test plan
Generated with Devin