Author: Nadali. Prepared with AI assistance.
What changed
On November 2, GitHub moved default blocking of the pull_request_target event from November 2 to December 2, 2026. Two trial restriction windows are scheduled beforehand: November 9 and 16, 16:00–18:00 UTC.
The rule concerns public repositories on GitHub Free, Team and Enterprise Cloud; private and internal repositories and Enterprise Server are outside this announcement’s scope.
Who benefits: business owners whose website or application is maintained by a team or contractor through a public repository. This changes the protection schedule for automated processes; it is neither a new AI feature nor a report that your website was breached.
A successful run does not establish safety
GitHub’s documentation explains the risk: this event runs with the base repository’s trust and access to its secrets. Executing untrusted code from an external change proposal in that context could expose those secrets.
The default policy currently operates in evaluate mode: a run can succeed even though enforcement would block it. It does not replace an existing applicable event policy. A blanket allowance merely to restore a green indicator is not a sound response.
What to ask the person responsible
Nadali’s editorial checking sequence:
- Establish whether the business has public repositories and who owns their automated checks. Having no in-house technical department does not answer that question: a contractor may maintain the repository.
- Request a short inventory of dependent processes: name, purpose, owner and consequence of interruption. Do not put passwords or keys in this document.
- Following the workflow governance instructions, review Policy insights for blocked or potentially blocked runs. Do not change policies without technical review.
- Before the first window, agree a decision for each necessary process and how its outcome will be checked. The developer should assess a safer trigger or justify a narrow exception rather than mechanically allowing everything.
- Record who will verify operation after the change. A message saying “configured” is not evidence that the required business process works.
Limits and takeaway
Nadali read the sources on November 3 but did not inspect customer repositories, execute workflows or change settings. Availability of modes for custom policies depends on the plan; these should not be confused with the described default policy.
Use the postponement to review dependencies, not as a reason to postpone security until December.
The cover is a reused conceptual Nadali AI illustration, not the GitHub interface or evidence of a completed inspection.
