use central signature in .github for CLA (#42)

parseablehq · Sep 16, 2023 · aabbbe0 · aabbbe0
1 parent ab63b44
commit aabbbe0
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 23 deletions.
diff --git a/.github/workflows/cla.yaml b/.github/workflows/cla.yaml
@@ -21,10 +21,10 @@ jobs:
         uses: contributor-assistant/[email protected]
         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 }}
+          PERSONAL_ACCESS_TOKEN: ${{ secrets.PERSONAL_ACCESS_TOKEN }}
         with:
+          remote-organization-name: 'parseablehq' # enter the remote organization name where the signatures should be stored (Default is storing the signatures in the same repository)
+          remote-repository-name: '.github' # enter the  remote repository name where the signatures should be stored (Default is storing the signatures in the same repository)
           path-to-signatures: 'signatures/version1/cla.json'
           path-to-document: 'https://github.com/parseablehq/.github/blob/main/CLA.md' # e.g. a CLA or a DCO document
           # branch should not be protected

diff --git a/signatures/version1/cla.json b/signatures/version1/cla.json