Skip to content

Commit

Permalink
test: Check if CLA works (#82)
Browse files Browse the repository at this point in the history
  • Loading branch information
gaocegege authored Nov 14, 2024
1 parent ecce473 commit 279b386
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions .github/workflows/cla.yml
Original file line number Diff line number Diff line change
Expand Up @@ -27,13 +27,13 @@ jobs:
with:
path-to-signatures: 'signatures/version1/cla.json'
path-to-document: 'https://gist.githubusercontent.com/gaocegege/92886a860e3648842e07651feb836719/raw/10663798a5e459707042a3d37bd6f89ac784dada/CLA.md' # e.g. a CLA or a DCO document
# branch should not be protected
# The branch is protected, but we use this: https://github.com/contributor-assistant/github-action/issues/150
branch: 'main'
allowlist: user1,bot*

# the followings are the optional inputs - If the optional inputs are not given, then default values will be taken
#remote-organization-name: enter the remote organization name where the signatures should be stored (Default is storing the signatures in the same repository)
#remote-repository-name: enter the remote repository name where the signatures should be stored (Default is storing the signatures in the same repository)
remote-organization-name: tensorchord
remote-repository-name: CLA
#create-file-commit-message: 'For example: Creating file for storing CLA Signatures'
#signed-commit-message: 'For example: $contributorName has signed the CLA in $owner/$repo#$pullRequestNo'
#custom-notsigned-prcomment: 'pull request comment with Introductory message to ask new contributors to sign'
Expand Down

0 comments on commit 279b386

Please sign in to comment.