Skepra / Web recovery & resilience

pull_request_target blocked by default December 2

GitHub is changing the default policy for pull_request_target in public repositories. Separate public repositories from private and internal ones, then rehearse the affected workflows before enforcement.

Discuss the next maintenance decision

Inventory before enforcement

Search public repositories for .github/workflows files using pull_request_target. Record the workflow purpose, permissions, secrets, fork inputs, checkout ref and whether the job executes code from an untrusted head. Ask whether the workflow needs base-repository context or can be redesigned as pull_request.

Use evaluate mode as a rehearsal

Use the policy view and Insights to see which runs the rule would block. Trigger a representative fork pull request in a non-production repository and record the commit, workflow run, event policy and resulting annotation.

Choose the smallest recovery route

If a delivery depends on a workflow, redesign the trigger, allow only a narrowly scoped trusted workflow or move the privileged step behind a reviewed service boundary. An allow rule needs an owner, review date and reason. A workflow that runs is not automatically safe if its token or checkout context changed.

Applicability and limits

This guide applies to public repositories using pull_request_target before the December 2, 2026 default enforcement. It does not claim that a particular repository is currently blocked or vulnerable.

Primary source: pull_request_target blocked by default December 2. Technical and editorial review remain pending.