ci: add CLA Assistant bot - #9
Merged
Merged
Conversation
Adds a self-hosted contributor-assistant workflow that asks contributors to sign the CLA (CLA.md) on their PRs and records signatures under signatures/. Also adds signatures/** to the Docker publish paths-ignore so signature commits don't trigger image rebuilds. Requires a repo secret PERSONAL_ACCESS_TOKEN (classic PAT, repo scope) for the bot to store signatures. Co-Authored-By: Claude Opus 4.8 <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.
Wires up the self-hosted contributor-assistant action so contributors sign the CLA on their PRs (needed to keep dual/commercial licensing open).
.github/workflows/cla.yml— comments on PRs, records signatures insignatures/version1/cla.json, bots allowlisted.signatures/**to the Docker publishpaths-ignoreso signature commits don't rebuild the image.One manual setup step: a repo admin must create a classic PAT (
reposcope) and add it as the repository secretPERSONAL_ACCESS_TOKEN— the bot needs it to store signatures.🤖 Generated with Claude Code