GitHub gives maintainers another month to review pull_request_target workflows

TechWork.bg

Талисманът Octocat пред лаптоп със сайта на GitHub / GitHub’s Octocat mascot in front of a laptop

Octocat in front of the GitHub homepage. Photo: Roman Synkevych / Unsplash.

Прочетете на български

Maintainers of public GitHub repositories have another month to identify Actions workflows that depend on pull_request_target. On 2 November, GitHub moved the date when it will block the event by default to 2 December.

Why this event matters

When someone proposes a change from a fork, an automation may need access to the base repository, for example to label the pull request. A workflow triggered by pull_request_target runs in the base repository’s context. If it also checks out and executes the contributor’s untrusted code, that code may gain access to secrets or be able to modify the repository.

Two trial windows before December

GitHub will temporarily enforce the rule on 9 and 16 November, from 16:00 to 18:00 UTC. Affected runs will be marked as failed without executing their workflows.

Maintainers can use Insights to see what the rule would block. If a bot only labels incoming requests, for example, its maintainer can review that workflow file and explicitly allow it if needed. The change covers public repositories on GitHub Free, Team and Enterprise Cloud. Private and internal repositories and GitHub Enterprise Server are outside its scope.

Sources

GitHub: revised enforcement schedule
Documentation: controlling workflow execution

TechWork.bg · Direct Search Partner

If you need world-class technology talent, contact us: business@techwork.bg