From 279b3869b51ba474fcff69b3ef80b530951e1c46 Mon Sep 17 00:00:00 2001 From: Ce Gao Date: Thu, 14 Nov 2024 15:47:06 +0800 Subject: [PATCH] test: Check if CLA works (#82) --- .github/workflows/cla.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/workflows/cla.yml b/.github/workflows/cla.yml index a5af7a8..7cd9939 100644 --- a/.github/workflows/cla.yml +++ b/.github/workflows/cla.yml @@ -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'