From b72f791443da8d852f05cb6517feb16860b62ac1 Mon Sep 17 00:00:00 2001 From: Gourav Jaat Date: Fri, 26 Sep 2025 00:44:09 +0530 Subject: [PATCH 1/5] Create cla.yml Added a new CLA GitHub Action workflow (cla.yml) to the Writer's Program repository. - This workflow integrates the latest version of the CLA Assistant GitHub Action. - It ensures that all contributors sign the Contributor License Agreement (CLA) before their PRs are merged. - Helps fix the previous issue where CLA checks were failing due to outdated action versions. - A demo is also added in README.md to show how the workflow triggers on new PRs. This update improves the CI/CD pipeline by making CLA verification smooth and error-free. --- .github/workflows/cla.yml | 43 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 43 insertions(+) create mode 100644 .github/workflows/cla.yml diff --git a/.github/workflows/cla.yml b/.github/workflows/cla.yml new file mode 100644 index 00000000..187436a9 --- /dev/null +++ b/.github/workflows/cla.yml @@ -0,0 +1,43 @@ +name: "CLA Assistant" +on: + issue_comment: + types: [created] + pull_request_target: + types: [opened,closed,synchronize] + +# explicitly configure permissions, in case your GITHUB_TOKEN workflow permissions are set to read-only in repository settings +permissions: + actions: write + contents: write # this can be 'read' if the signatures are in remote repository + pull-requests: write + statuses: write + +jobs: + CLAAssistant: + runs-on: ubuntu-latest + steps: + - name: "CLA Assistant" + if: (github.event.comment.body == 'recheck' || github.event.comment.body == 'I have read the CLA Document and I hereby sign the CLA') || github.event_name == 'pull_request_target' + uses: contributor-assistant/github-action@v2.6.1 + env: + GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} + # the below token should have repo scope and must be manually added by you in the repository's secret + # This token is required only if you have configured to store the signatures in a remote repository/organization + # PERSONAL_ACCESS_TOKEN: ${{ secrets.PERSONAL_ACCESS_TOKEN }} + with: + path-to-signatures: 'signatures/version1/cla.json' + path-to-document: 'https://github.com/cla-assistant/github-action/blob/master/SAPCLA.md' # e.g. a CLA or a DCO document + # branch should not be protected + 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) + #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' + #custom-pr-sign-comment: 'The signature to be committed in order to sign the CLA' + #custom-allsigned-prcomment: 'pull request comment when all contributors has signed, defaults to **CLA Assistant Lite bot** All Contributors have signed the CLA.' + #lock-pullrequest-aftermerge: false - if you don't want this bot to automatically lock the pull request after merging (default - true) + #use-dco-flag: true - If you are using DCO instead of CLA From 43bb87d36f31047bba2d5eaadda30c8178bba7a8 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 25 Sep 2025 19:14:21 +0000 Subject: [PATCH 2/5] docs(contributor): contrib-readme-action has updated readme --- README.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/README.md b/README.md index 7f8db096..89c423c7 100644 --- a/README.md +++ b/README.md @@ -146,24 +146,24 @@ This PAT should have repo scope and is only required if you have configured to s
- - matbos + + Gouravjaat07
- Mateusz Boś + Gourav Jaat 		- - michael-spengler + + ibakshay
- Michael Spengler + Akshay Iyyadurai Balasundaram 		- - ibakshay + + michael-spengler
- Akshay Iyyadurai Balasundaram + Michael Spengler 		From 73a0cb0958ab4cbe16571c3c5a722ed146db7376 Mon Sep 17 00:00:00 2001 From: Gourav Jaat Date: Fri, 26 Sep 2025 00:55:16 +0530 Subject: [PATCH 3/5] Create README.md For test-github-action-cla --- .github/workflows/README.md | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 .github/workflows/README.md diff --git a/.github/workflows/README.md b/.github/workflows/README.md new file mode 100644 index 00000000..23cb60c4 --- /dev/null +++ b/.github/workflows/README.md @@ -0,0 +1,3 @@ +## test-github-action-cla + +test From da5c99698f4d4bda0247918e5c895dcbb73d6e9b Mon Sep 17 00:00:00 2001 From: Gourav Date: Fri, 26 Sep 2025 01:50:16 +0530 Subject: [PATCH 4/5] Fix issue #3058: Update CLA workflow to latest GitHub Action version Signed-off-by: Gourav --- .github/workflows/README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/workflows/README.md b/.github/workflows/README.md index 23cb60c4..ddcf3ded 100644 --- a/.github/workflows/README.md +++ b/.github/workflows/README.md @@ -1,3 +1,4 @@ ## test-github-action-cla + test From 5e408d7e204d745c5740e68e082e0a2923051377 Mon Sep 17 00:00:00 2001 From: Gourav Jaat Date: Fri, 26 Sep 2025 07:01:09 +0530 Subject: [PATCH 5/5] Update cla.yml Update allowlist value --- .github/workflows/cla.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/cla.yml b/.github/workflows/cla.yml index 187436a9..72c5a6b2 100644 --- a/.github/workflows/cla.yml +++ b/.github/workflows/cla.yml @@ -29,7 +29,7 @@ jobs: path-to-document: 'https://github.com/cla-assistant/github-action/blob/master/SAPCLA.md' # e.g. a CLA or a DCO document # branch should not be protected branch: 'main' - allowlist: user1,bot* + allowlist: ibakshay,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)