Skip to content

Commit c99e960

Browse files
committed
CLA Assistant
1 parent 6d4f768 commit c99e960

2 files changed

Lines changed: 49 additions & 0 deletions

File tree

.github/workflows/cla.yml

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
name: "CLA Assistant"
2+
on:
3+
issue_comment:
4+
types: [created, edited]
5+
issues:
6+
types: [created, edited]
7+
pull_request_target:
8+
types: [opened,closed,synchronize]
9+
10+
# explicitly configure permissions, in case your GITHUB_TOKEN workflow permissions are set to read-only in repository settings
11+
permissions:
12+
actions: write
13+
contents: write # this can be 'read' if the signatures are in remote repository
14+
pull-requests: write
15+
statuses: write
16+
17+
jobs:
18+
CLAAssistant:
19+
runs-on: ubuntu-latest
20+
steps:
21+
- name: "CLA Assistant"
22+
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'
23+
uses: contributor-assistant/github-action@v2.4.0
24+
env:
25+
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
26+
# the below token should have repo scope and must be manually added by you in the repository's secret
27+
# This token is required only if you have configured to store the signatures in a remote repository/organization
28+
PERSONAL_ACCESS_TOKEN: ${{ secrets.PERSONAL_ACCESS_TOKEN }}
29+
with:
30+
path-to-signatures: 'signatures/version1/cla.json'
31+
path-to-document: 'https://github.com/fido-alliance/fido-device-onboard-feedback/blob/main/FIDO_CLA.md' # e.g. a CLA or a DCO document
32+
# branch should not be protected
33+
branch: 'main'
34+
allowlist: user1,bot*
35+
36+
# the followings are the optional inputs - If the optional inputs are not given, then default values will be taken
37+
#remote-organization-name: enter the remote organization name where the signatures should be stored (Default is storing the signatures in the same repository)
38+
#remote-repository-name: enter the remote repository name where the signatures should be stored (Default is storing the signatures in the same repository)
39+
#create-file-commit-message: 'For example: Creating file for storing CLA Signatures'
40+
#signed-commit-message: 'For example: $contributorName has signed the CLA in $owner/$repo#$pullRequestNo'
41+
#custom-notsigned-prcomment: 'pull request comment with Introductory message to ask new contributors to sign'
42+
#custom-pr-sign-comment: 'The signature to be committed in order to sign the CLA'
43+
#custom-allsigned-prcomment: 'pull request comment when all contributors has signed, defaults to **CLA Assistant Lite bot** All Contributors have signed the CLA.'
44+
#lock-pullrequest-aftermerge: false - if you don't want this bot to automatically lock the pull request after merging (default - true)
45+
#use-dco-flag: true - If you are using DCO instead of CLA

signatures/version1/cla.json

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
{
2+
"signedContributors": [
3+
]
4+
}

0 commit comments

Comments
 (0)