otterize/CLA assistant lite

An action to handle the Contributor License Agreement (CLA) and Developer Certificate of Orgin (DCO)

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stalelast commit Sep 20, 2022
License
Apache 2.0
Runtime
Deprecated runtime

Pinned Snippet

workflow.ymlSHA-pinned
uses: otterize/cla-bot@aa0858c4bcff3841bdb4d09794f856373eef03de # v2.2.1-otterize

tags can be moved; commit SHAs can't. why a SHA?

Inputs

namedescriptionrequireddefault
path-to-signaturesGive a path for storing CLAs in a json file —./signatures/cla.json
branchprovide a branch where all the CLAs are stored—master
allowlistusers in the allow list don't have to sign the CLA document—""
remote-repository-nameprovide the remote repository name where all the signatures should be stored——
remote-organization-nameprovide the remote organization name where all the signatures should be stored——
path-to-documentFully qualified web link to the document - example: https://github.com/cla-assistant/github-action/blob/master/SAPCLA.md——
signed-commit-messageCommit message when a new contributor signs the CLA in a PR——
signed-empty-commit-messageCommit message when a new contributor signs the CLA (empty)——
create-file-commit-messageCommit message when a new file is created——
custom-notsigned-prcommentIntroductory message to ask new contributors to sign——
custom-pr-sign-commentThe signature to be committed in order to sign the CLA.——
custom-allsigned-prcommentpull request comment when everyone has signed, defaults to **CLA Assistant Lite** All Contributors have signed the CLA.——
use-dco-flagSet this to true if you want to use a dco instead of a cla—false
lock-pullrequest-aftermergeWill lock the pull request after merge so that the signature the contributors cannot revoke their signature comments after merge—true

Outputs

no outputs