The GitHub Actions brownout scheduled for November 16 can mark a pull_request_target workflow as failed before a single job starts. In a November 9 test, blog author Nilay Kabariya reported that the trigger failed even for a pull request from a branch inside the same public repository. A parallel pull_request workflow succeeded on the same push, according to Kabariya's account.

GitHub has scheduled the next brownout for November 16, 2026, from 16:00 to 18:00 UTC, ahead of permanent enforcement on December 2, according to its announcement. Blocked attempts will create failed runs with an error annotation, and the workflows will not execute.

Which Repositories Face the GitHub Actions Brownout

The announced scope includes public repositories on GitHub Free, Team and Enterprise Cloud. Private and internal repositories, along with GitHub Enterprise Server, fall outside it. The restriction concerns the pull_request_target event, which starts a workflow in the context of the repository receiving a pull request.

Only attempts blocked by the default rule fail during the brownout; workflows explicitly allowed by an applicable policy can proceed, Agent Upstart reported November 13. The default event policy does not replace an applicable policy already configured.

After the temporary window, GitHub says the default rule returns to evaluation mode, permitting workflows with warnings. Kabariya's earlier November 8 evaluation test, however, completed without a warning about the approaching restriction. His subsequent brownout test ended with startup_failure and zero jobs started.

Agent Upstart points out that a quiet window without triggered workflows does not test their behavior. Kabariya's same-repository result also illustrates why the event name and applicable policy matter even when a pull request does not originate in an outside fork.

Why the Trigger Carries Extra Risk

The security issue is the authority available to the workflow. A pull_request_target workflow receives the base repository's token and can access repository and organization secrets, according to GitHub's security documentation. Its workflow and default checkout come from the base repository's default branch.

Fork code does not execute automatically. The dangerous combination arises when a privileged workflow checks out untrusted fork code and then runs its scripts, installs dependencies or consumes attacker-controlled configuration. Those operations can turn a contribution into code execution with access to privileged credentials.

For fork pull requests, the pull_request event uses a read-only token and withholds other secrets. GitHub recommends that trigger when extra secret access is unnecessary. Retaining the default block preserves the protection; explicitly allowing a reviewed pull_request_target workflow permits that privileged automation to continue. GitHub supports targeting selected workflow files when configuring an allowance.

S5 Labs analysis author Joshua Wendt identified narrower enforcement wording in GitHub's security documentation than in its changelog in his November 12 analysis.

Policy Insights Shows Anticipated Failures

Repository administrators, organization owners and enterprise owners can manage execution protections. For repositories and organizations, execution protections are configured under Settings, Actions, then Policies, according to GitHub's workflow execution documentation.

Selecting Evaluate when configuring a policy is an Enterprise Cloud feature. GitHub recommends reviewing privileged workflows before explicitly allowing pull_request_target.

Policy insights sits directly below the Actions policies page in the account sidebar. It displays runs blocked by active policies and runs that evaluation policies would have blocked, giving administrators a view of affected attempts before permanent enforcement.

For more on this topic, see our Technology coverage.

Image: AI-generated image.