[CI] Remove pull_request_target event workflows #55392

Activity

1. raulcd

   added

   Type: enhancement

   on Nov 4, 2026
2. github-actions

   added

   Component: Continuous Integration

   on Nov 4, 2026
3. raulcd commented on Nov 4, 2026

   

   raulcd

   on Nov 4, 2026

   MemberAuthor

   More actions

   For .github/workflows/pr_limit.yml we can migrate to the .asf.yaml functionality (collaborators won't be covered here).
   For .github/workflows/pr_bot.yml we should just remove the whole awaiting review, awaiting change, etc as it creates noise and has never really worked.
   For the .github/workflows/dev_pr.yml I have to explore a little further to come up with ideas.

   @kou @pitrou @thisisnic thoughts? I am happy to start working on the first two. I might split in sub-issues one per workflow.

   👍React with 👍1Reacted by Rok Mihevc
4. raulcd commented on Nov 4, 2026

   

   raulcd

   on Nov 4, 2026

   MemberAuthor

   More actions

   It seems datafusion is coming up with a two workflows approach for the labelers:

   • ci: migrate pull_request_target workflows to workflow_run datafusion#26683

   As @andygrove points here:

   Move to the two-workflow pattern that apache/datafusion#26683 uses:

   1. A pull_request workflow with no write access records the PR number (and the changed paths, if needed) and uploads it as an artifact.
   2. A workflow_run workflow, triggered when the first one completes, runs in the base repository context with pull-requests: write, reads the artifact, and applies the labels from .github/workflows/dev_pr/labeler.yml. It treats the artifact as untrusted data and never checks out or runs PR code.
5. raulcd

   added sub-issues on Nov 5, 2026

   • [CI] Replace the PR Limit workflow with the .asf.yaml pull request creation cap #55163
   • [CI][Dev] Remove pull_request_target for workflow labels "awaiting xxx" #55411
6. kou commented on Nov 5, 2026

   

   kou

   on Nov 5, 2026

   Member

   More actions

   For .github/workflows/pr_limit.yml we can migrate to the .asf.yaml functionality (collaborators won't be covered here).

   +1

   For .github/workflows/pr_bot.yml we should just remove the whole awaiting review, awaiting change, etc as it creates noise and has never really worked.

   +1

   For the .github/workflows/dev_pr.yml I have to explore a little further to come up with ideas.

   How about using only pull_request instead of pull_request + workflow_run? We will lost some current functions but it will not introduce complexities.
7. raulcd

   added a sub-issue on Nov 10, 2026

   • [Dev] Remove pull_request_target from dev_pr workflow #55473
8. github-actions

   assigned

   raulcd

   on Nov 10, 2026