Description

iccir

opened on Sep 25, 2026

Issue body actions

Summary

While checking the results from our PR Greetings action, I noticed the following message:

On December 2, 2026, GitHub will restrict pull_request_target on public repositories by default. To continue allowing the event trigger, configure an Actions policy. Learn more: https://gh.io/securely-using-pull_request_target#default-policy-for-pull_request_target

Proposed fix

I believe that someone with access needs to update the Actions policy.

Edit: GitHub has moved the date to December 2.

Reacted by Melissa Weber Mendonça

Activity

1. iccir

   added

   Maintenance

   on Sep 25, 2026
2. QuLogic commented on Sep 25, 2026

   

   QuLogic

   on Sep 25, 2026

   Member

   More actions

   I looked over the workflows and AFAICT, they are following best practices and should be secure. Unfortunately, though those docs say that the policy is now running in evaluate mode, we can't actually see those insights withou an Enterprise subscription.

   But we still have a bit of time to fully investigate the workflows before the restrictions are in place
3. greglucas commented on Oct 17, 2026

   

   greglucas

   on Oct 17, 2026

   Contributor

   More actions

   I think the action is for someone with admin rights on the repo to create an event policy allowing pull_request_target for the 4 workflows: labeler.py, conflictcheck.py, pr_welcome.py, autoclose_comment.py.

   I looked over the workflows and AFAICT, they are following best practices and should be secure.

   I agree, we have removed all permissions on those workflows and the issue is if we pull the actual PR code and run it which those aren't interacting with rather just labeling things based on the trigger itself.

   Reacted by Ricci Adams
4. iccir commented on Oct 17, 2026

   

   iccir

   on Oct 17, 2026

   ContributorAuthor

   More actions

   3. I think the action is for someone with admin rights on the repo to create an event policy allowing pull_request_target for the 4 workflows: labeler.py, conflictcheck.py, pr_welcome.py, autoclose_comment.py.

   That was my understanding from the linked document. I believe that these 4 workflows should be secure per the comment in zizmor.yml:

         # These workflows use pull_request_target solely to obtain write access
         # for API operations (labeling, commenting) on fork PRs. None of them
         # check out or execute any PR-supplied code.
   

   However, someone should double-check that before making the explicit policies.
5. iccir

   changed the title [-][MNT]: GitHub will restrict `pull_request_target` on November 2, 2026[/-] [+][MNT]: GitHub will restrict `pull_request_target` on December 2, 2026[/+] on Oct 26, 2026
6. iccir commented on Oct 26, 2026

   

   iccir

   on Oct 26, 2026

   ContributorAuthor

   More actions

   It looks like GitHub changed the deadline to December 2:

   On December 2, 2026, GitHub will enforce the default policy for affected repositories that were using the default pull_request_target policy before general availability.
7. melissawm commented on Nov 3, 2026

   

   melissawm

   on Nov 3, 2026

   Member

   More actions

   I think i have a workaround to remove usage of pull_request_target on these actions. I will send in a PR shortly.

Issue actions