From 0b421984edd0a3a27f8efffb01f18d0cb11508e8 Mon Sep 17 00:00:00 2001 From: asyncapi-bot Date: Fri, 8 May 2026 10:37:21 +0000 Subject: [PATCH] ci: update of files from global .github repo --- ...umans-add-ready-to-merge-or-do-not-merge-label.yml | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/.github/workflows/automerge-for-humans-add-ready-to-merge-or-do-not-merge-label.yml b/.github/workflows/automerge-for-humans-add-ready-to-merge-or-do-not-merge-label.yml index 99078d37..52d42f47 100644 --- a/.github/workflows/automerge-for-humans-add-ready-to-merge-or-do-not-merge-label.yml +++ b/.github/workflows/automerge-for-humans-add-ready-to-merge-or-do-not-merge-label.yml @@ -37,7 +37,10 @@ jobs: env: GITHUB_ACTOR: ${{ github.actor }} with: - github-token: ${{ github.token }} + # Use bot PAT, not the default GITHUB_TOKEN: events created by + # GITHUB_TOKEN do not trigger other workflows, so `Automerge For + # Humans` would never see the `labeled` event. + github-token: ${{ secrets.GH_TOKEN }} script: | const prDetailsUrl = context.payload.issue.pull_request.url; const { data: pull } = await github.request(prDetailsUrl); @@ -93,7 +96,8 @@ jobs: - name: Add do-not-merge label uses: actions/github-script@v7 with: - github-token: ${{ github.token }} + # Bot PAT so the `labeled` event can trigger downstream workflows. + github-token: ${{ secrets.GH_TOKEN }} script: | github.rest.issues.addLabels({ issue_number: context.issue.number, @@ -119,7 +123,8 @@ jobs: - name: Add autoupdate label uses: actions/github-script@v7 with: - github-token: ${{ github.token }} + # Bot PAT so the `labeled` event can trigger the autoupdate workflow. + github-token: ${{ secrets.GH_TOKEN }} script: | github.rest.issues.addLabels({ issue_number: context.issue.number,