From ba1d0419a814de29825ef3c9dbccc4b92416513f Mon Sep 17 00:00:00 2001 From: Stanislas Date: Wed, 10 Dec 2025 18:23:58 +0100 Subject: [PATCH] fix: use PAT to trigger CI after hash update (#1337) - Commits made with `GITHUB_TOKEN` don't trigger workflows - Using a PAT allows the hash update commit to trigger CI checks - Fixes the issue where PR #1335 didn't have CI triggered after the hash update --- .github/workflows/update-easyrsa-hash.yml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/.github/workflows/update-easyrsa-hash.yml b/.github/workflows/update-easyrsa-hash.yml index 283a180..7ae7028 100644 --- a/.github/workflows/update-easyrsa-hash.yml +++ b/.github/workflows/update-easyrsa-hash.yml @@ -1,8 +1,9 @@ name: Update Easy-RSA SHA256 # Note: This workflow commits and pushes changes to openvpn-install.sh. -# Infinite recursion is prevented because pushes made with GITHUB_TOKEN do not trigger workflows. -# See: https://docs.github.com/en/actions/using-workflows/triggering-a-workflow#preventing-workflow-runs-from-recursively-generating-new-workflow-runs +# Uses PAT to trigger CI on the resulting commit. Infinite recursion is prevented +# by the 'renovate/' branch prefix check - CI commits don't re-trigger this workflow. +# Requires: Create a PAT with 'contents: write' scope and add as repository secret 'PAT' on: pull_request: @@ -23,7 +24,7 @@ jobs: - uses: actions/checkout@v4 with: ref: ${{ github.head_ref }} - token: ${{ secrets.GITHUB_TOKEN }} + token: ${{ secrets.PAT }} - name: Extract version and update SHA256 run: |