Skip to content

Fix the CLA check: allowlist the maintainer's GitHub login - #20

Merged
nicholas9182 merged 1 commit into
mainfrom
fix/cla-workflow
Sep 29, 2026
Merged

nicholas9182 merged 1 commit into
mainfrom
fix/cla-workflow

Conversation

@nicholas9182

Copy link
Copy Markdown
Collaborator

Why

The CLA Assistant allowlist listed nsiemons, a git author name. The maintainer's commits are attributed to the GitHub login nicholas9182, so the bot asked the repo owner to sign.

What

  • The allowlist uses nicholas9182 (bots unchanged); comments explain why.
  • The cla-signatures branch the action stores signatures on exists. Existing signatures are untouched; where the branch was missing, it was created with an empty signatures/cla.json.

Note

cla.yml runs on pull_request_target, so GitHub runs the workflow from main, not from this PR. After merge, commenting recheck on this PR runs the fixed workflow.

Same fix as stanford-developers/steer-app-kit-fastapi#4.

🤖 Generated with Claude Code

The allowlist named 'nsiemons', which is a git author name, not a GitHub login.
The maintainer's commits are attributed to nicholas9182, so the bot asked the
repo owner to sign.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@nicholas9182
nicholas9182 merged commit 84d99f0 into main Sep 29, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant