From 6307893febb2cd45b963ce1cbab4479cee053033 Mon Sep 17 00:00:00 2001
From: Artem Chepurnoy <artemchep@gmail.com>
Date: Sat, 30 Dec 2023 10:50:34 +0200
Subject: [PATCH] feat: Test CLA Assistant integration

---
 .github/workflows/cla.yml | 48 +++++++++++++++++++++++++++++++++++++++
 SAPCLA.md                 |  1 +
 2 files changed, 49 insertions(+)
 create mode 100644 .github/workflows/cla.yml
 create mode 100644 SAPCLA.md

diff --git a/.github/workflows/cla.yml b/.github/workflows/cla.yml
new file mode 100644
index 00000000..362e0c1a
--- /dev/null
+++ b/.github/workflows/cla.yml
@@ -0,0 +1,48 @@
+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
+  pull-requests: write
+  statuses: write
+
+jobs:
+  cla-assistant:
+    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.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_TOKEN }}
+        with:
+          path-to-signatures: 'cla/version1/cla.json'
+          path-to-document: 'https://github.com/AChep/keyguard-app/blob/master/SAPCLA.md'
+          # branch should not be protected
+          branch: 'master'
+          allowlist: AChep,dependabot
+
+          # 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
diff --git a/SAPCLA.md b/SAPCLA.md
new file mode 100644
index 00000000..345e6aef
--- /dev/null
+++ b/SAPCLA.md
@@ -0,0 +1 @@
+Test