From 9acdc6fda13fd07fe1f6412d3a0eb3d859e4990b Mon Sep 17 00:00:00 2001 From: "Jose R. Gonzalez" Date: Wed, 13 Sep 2023 16:13:48 -0500 Subject: [PATCH] Use GITHUB_TOKEN to approve PRs instead instead of the bot This has historically used a token provided by a maintainer. That token was revoked and the bot's token was used instead, but we run into issues approving PRs because the bot is also the submitter of the PR. This works around that issue. --- .github/workflows/build.yml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml index a2128e3cf6c..6721c65bb3f 100644 --- a/.github/workflows/build.yml +++ b/.github/workflows/build.yml @@ -306,7 +306,11 @@ jobs: if: ${{ steps.check_report.conclusion == 'success' }} uses: hmarr/auto-approve-action@v2 with: - github-token: ${{ secrets.BOT_TOKEN }} + # Using the GitHub Token here is a temporary fix because the bot cannot + # approve their own PRs. Long-term solution will likely be to create a + # second BOT account to use here, or change the production workflows + # to use GITHUB_TOKEN for this task to match this repo. + github-token: ${{ secrets.GITHUB_TOKEN }} - name: Merge PR id: merge_pr