Skip to content

fix(cla): write CLA signatures to this repo, not a remote (drops PAT requirement) #30

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
HBarefoot merged 1 commit into from
Jun 7, 2026
Merged

fix(cla): write CLA signatures to this repo, not a remote (drops PAT requirement) #30

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions .github/workflows/cla.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,11 @@ jobs:
path-to-document: 'https://github.com/HBarefoot/engram/blob/main/CLA.md'
branch: 'cla-signatures'
allowlist: HBarefoot,dependabot[bot]
remote-organization-name: HBarefoot
remote-repository-name: engram
# Signatures live on the `cla-signatures` branch of THIS repo, so the
# default GITHUB_TOKEN (with contents:write above) suffices. The
# remote-organization-name / remote-repository-name inputs were
# removed: they make the action target a *separate* repo and demand a
# PERSONAL_ACCESS_TOKEN, which failed every run with "Please add a
# personal access token … for writing signatures in a remote repo".
custom-pr-sign-comment: 'I have read the CLA Document and I hereby sign the CLA'
custom-allsigned-prcomment: 'All contributors have signed the CLA. ✓'
Loading