Repository navigation
Avoiding pull_request_target usage in workflows #3864
Description
One of this repositories workflow's uses pull_request_target:
Please see the GitHub documentation for a list of risks associated with the target. I see the workflow is currently quite careful, but IMO it is still better to split it into two, one for building and one for posting.
It is now disallowed by actions/checkout (see blog post). We are also considering disabling it across the organisation (new feature), but it would break this workflow.
Activity
StanFromIreland commentedon Jun 18, 2026
Also looking at the workflow, I see you use
tj-actions/changed-files:python-docs-es/.github/workflows/pr-comment.yml
Line 40 in 9b99734
Note that the action was compromised in a supply chain attack last year. I suggest hash-pinning all Actions (and running Zizmor too :-).