Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

The Nov 16 pull_request_target brownout, in UTC

Written November 13, 2026

For two hours on November 16 (16:00–18:00 UTC), GitHub breaks pull_request_target on purpose. How to use the window to find what will fail Dec 2.

The window

On Monday, November 16, from 16:00 to 18:00 UTC, GitHub will enforce its new default rule against pull_request_target for two hours, then switch it back off. GitHub's changelog calls these scheduled windows brownouts. This is the second one; the first ran on November 9 at the same hours. Both are rehearsals for December 2, when the block becomes permanent.

During the window, a pull_request_target attempt that the default rule blocks creates a failed run with an error annotation, and the workflow does not execute. When the window closes, the rule returns to evaluate mode: workflows run again, with warnings. Nothing about your repository changes at 18:00. The only lasting output of the two hours is the list of failures.

Who is in scope

The reason for the rule is the trigger itself. pull_request_target runs in the context of the base repository and can access its secrets. If such a workflow executes untrusted code from a fork, that code can compromise the pipeline or steal the secrets. The default rule exists to make that pattern opt-in instead of automatic.

How to use the two hours

A brownout only teaches you something if your workflows actually fire during it. A quiet repository learns nothing at 16:00 and is surprised on December 2 instead. The practical moves:

Before Monday

There is also work that does not need the window at all. The rule already runs in evaluate mode, which means GitHub is currently recording the runs it would block while letting them pass with warnings. Insights holds that list today. A maintainer who reads it before Monday can fix policies in an ordinary change, and use the brownout only to confirm the fix under real enforcement.

Warn your contributors, too. A fork pull request opened during the window can produce a red, failed run that has nothing to do with the contributor's code. Two hours of confused comments is a predictable cost of the rehearsal; a note on the repository before 16:00 UTC removes most of it. After 18:00 the warnings return, and the same pull request runs again — the failure is a message about December, not a verdict on the change.

The December date behind it

From December 2, 2026, the same block applies permanently to public repositories, unless an event policy allows the workflow. That change was first scheduled for November 2 and moved. The full enforcement picture, including what to do about workflows that genuinely need the trigger, sits in GitHub blocks pull_request_target workflows on December 2. The November 16 window is the last scheduled chance to watch your own workflows fail under the rule while failure is still free.

Related playbooks

Sources

Back to: Coding playbooks hub · Also: GitHub blocks pull_request_target workflows on December 2