From a442e1edfadf0ad5371680ec7736f5702bd44426 Mon Sep 17 00:00:00 2001 From: Kevin Longe <273747162+kvlonge@users.noreply.github.com> Date: Mon, 16 Nov 2026 17:46:25 +0000 Subject: [PATCH] fix: request auto-merge on pull_request instead of pull_request_target GitHub blocks pull_request_target in public repositories by default from 2 December 2026, which stops this required workflow from starting and keeps pull requests out of the merge queue. The job checks out no pull request code and already skips forks, and same-repository pull_request runs receive the secrets it needs, so pull_request is enough. --- .github/workflows/auto-merge.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/.github/workflows/auto-merge.yml b/.github/workflows/auto-merge.yml index 33145e6..47faa6c 100644 --- a/.github/workflows/auto-merge.yml +++ b/.github/workflows/auto-merge.yml @@ -1,7 +1,10 @@ name: Request Auto-Merge on: - pull_request_target: + # pull_request rather than pull_request_target: GitHub blocks pull_request_target in public + # repositories by default. The job checks out no pull request code and runs only for branches + # in the same repository, which receive secrets under pull_request. + pull_request: types: [opened, synchronize, reopened, ready_for_review] # Repositories with a merge queue require this workflow on the queue's merge groups too. There is # nothing to request there; the merge-group job only lets the run conclude as a success. @@ -21,7 +24,7 @@ jobs: request-auto-merge: if: >- - github.event_name == 'pull_request_target' && + github.event_name == 'pull_request' && !github.event.pull_request.draft && github.event.pull_request.head.repo.full_name == github.repository runs-on: ubuntu-latest