From d0d12ce628f9a4c90ba0561b9e34da3ea3b4db6d Mon Sep 17 00:00:00 2001 From: Andor Kesselman Date: Thu, 18 May 2023 09:35:21 +0530 Subject: [PATCH 1/2] wip: fixing easy cla --- .github/workflows/glossary.yml | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) diff --git a/.github/workflows/glossary.yml b/.github/workflows/glossary.yml index d626c69..e9be4ac 100644 --- a/.github/workflows/glossary.yml +++ b/.github/workflows/glossary.yml @@ -15,6 +15,12 @@ on: required: false default: gh_pages description: This is where the output of script will be pushed to. +# explicitly configure permissions, in case your GITHUB_TOKEN workflow permissions are set to read-only in repository settings +permissions: + actions: write + contents: write + pull-requests: write + statuses: write jobs: build: @@ -46,6 +52,32 @@ jobs: git config user.name "GitHub Actions Bot" git config user.email "<>" + - 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.3.0 + 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 + - name: Publishing run: | git fetch origin From 72b8fcfe8e1748ecbd5c65c3ce84c508f7e1b4ed Mon Sep 17 00:00:00 2001 From: Andor Kesselman Date: Fri, 23 Jun 2023 00:36:28 +0530 Subject: [PATCH 2/2] Update glossary.yml --- .github/workflows/glossary.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/glossary.yml b/.github/workflows/glossary.yml index e9be4ac..eaa9c49 100644 --- a/.github/workflows/glossary.yml +++ b/.github/workflows/glossary.yml @@ -59,7 +59,7 @@ jobs: 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 }} + PERSONAL_ACCESS_TOKEN: ${{ secrets.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