fix(cla): write CLA signatures to this repo, not a remote (drops PAT requirement)#30
Merged
Merged
Conversation
…irement) The CLA Assistant failed on every PR with "Please add a personal access token as an environment variable for writing signatures in a remote repository/organization" — before it ever evaluated the allowlist. `remote-organization-name`/`remote-repository-name` make the action target a separate repo, which requires a PERSONAL_ACCESS_TOKEN; only GITHUB_TOKEN was provided. Signatures are meant to land on this repo's own `cla-signatures` branch, so those two inputs are removed and the default GITHUB_TOKEN (with the existing contents:write permission) is sufficient. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
1 participant
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.
The CLA Assistant check fails on every PR (e.g. #29) with:
…and errors out before it evaluates the allowlist, so even allowlisted maintainers can't get a green check.
Cause
.github/workflows/cla.ymlpassesremote-organization-name: HBarefoot+remote-repository-name: engram. Those inputs makecontributor-assistant/github-actiontarget a separate repo for signature storage, which requires aPERSONAL_ACCESS_TOKEN— but the workflow only providesGITHUB_TOKEN.Fix
Signatures are meant to live on this repo's own
cla-signaturesbranch, so the tworemote-*inputs are removed. The defaultGITHUB_TOKEN(with the existingcontents: writepermission) can then create/write that branch.Note on rollout
cla.ymlruns onpull_request_target, which always uses the base branch's copy of the workflow. So this fix only takes effect once it's merged tomain; afterward, commentingrecheckon open PRs (incl. #29) re-runs the check, which will pass for the allowlisted maintainer.🤖 Generated with Claude Code