Repository navigation
ci(cla): use the org PERSONAL_ACCESS_TOKEN for the CLA check - #302
Merged
Merged
Conversation
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 <noreply@anthropic.com>
adityamehra
approved these changes
Oct 30, 2026
adityamehra
left a comment
adityamehra
left a comment
Member
There was a problem hiding this comment.
LGTM! PERSONAL_ACCESS_TOKEN from org will get picked up
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
PERSONAL_ACCESS_TOKENin the CLA workflow instead of the repo-levelPAT_CLATOOL, as in Chore: use org PAT #231.PAT_CLATOOLcannot write tosplunk/cla-agreement, so the check fails for new signers.PERSONAL_ACCESS_TOKENis refreshed. It last updated on 2026-07-09 and returned 401 on Oct 7.Test plan
🤖 Generated with Claude Code