# De-fanging dangerous triggers in GitHub Actions across an organization

Source: [Python Software Foundation News](https://pyfound.blogspot.com/2026/11/de-fanging-dangerous-triggers-in-github.html) · 2026-11-18 · Languages
Page: https://themorning.dev/story/de-fanging-dangerous-triggers-in-github-actions-across-an-organization-c1224af285691117
Kind: policy · Impact: medium

## In brief

- On December 2, 2026, GitHub will start blocking the pull_request_target trigger by default in public repositories.
- The Python Software Foundation published a post by Mike Fiedler and Seth Larson explaining the change and the risks of this trigger.

## Why it matters

Public repositories whose workflows rely on pull_request_target will no longer run them by default after the change, so maintainers need to check their workflows before the date.

## What to do

- Review GitHub Actions workflows that use pull_request_target before December 2, 2026

## Timeline

- 2026-12-02: GitHub starts blocking pull_request_target by default in public repositories

## Coverage

- [De-fanging dangerous triggers in GitHub Actions across an organization](https://pyfound.blogspot.com/2026/11/de-fanging-dangerous-triggers-in-github.html) — Python Software Foundation News, 2026-11-18

Tags: github-actions, ci-cd, security, workflows, github

---

Brief generated by AI (claude-haiku-5-5) from the reporting listed under Coverage. Headlines belong to their publishers. The Morning Dev – https://themorning.dev
