From 7e0309192bfe2d75c8bba5ed271ae085ca67ef3f Mon Sep 17 00:00:00 2001 From: etserend Date: Fri, 30 Oct 2026 13:29:44 -0500 Subject: [PATCH] ci(cla): use the org PERSONAL_ACCESS_TOKEN for the CLA check The repo-level PAT_CLATOOL can read the signature store but cannot write to splunk/cla-agreement, so the CLA check fails for any new signer ("Could not update the JSON file: Resource not accessible by personal access token"). Read the org-level PERSONAL_ACCESS_TOKEN instead, as in #231. Co-Authored-By: Claude Code --- .github/workflows/cla.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/cla.yml b/.github/workflows/cla.yml index 59c35937..4d6773db 100644 --- a/.github/workflows/cla.yml +++ b/.github/workflows/cla.yml @@ -20,7 +20,7 @@ jobs: uses: contributor-assistant/github-action@ca4a40a7d1004f18d9960b404b97e5f30a505a08 # v2.6.1 env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} - PERSONAL_ACCESS_TOKEN: ${{ secrets.PAT_CLATOOL }} + PERSONAL_ACCESS_TOKEN: ${{ secrets.PERSONAL_ACCESS_TOKEN }} with: remote-organization-name: splunk remote-repository-name: cla-agreement