-
Notifications
You must be signed in to change notification settings - Fork 2
69 lines (65 loc) · 3.63 KB
/
cla.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
# How to implement the workflow in repository
# Create a .github/workflows/cla.yaml file in the repository and copy code below
# ###################################################
# name: CLA Assistant
# on:
# issue_comment:
# types: [created]
# pull_request_target:
# types: [opened,closed,synchronize]
# jobs:
# cla_assistant:
# uses: Netcracker/qubership-github-workflows/.github/workflows/cla.yaml@main
# secrets:
# personal_access_token: ${{ secrets.PERSONAL_ACCESS_TOKEN }}
# ###################################################
# PERSONAL_ACCESS_TOKEN should be created for Netcracker/cla-storage with repository permissions
# - Read access to metadata
# - Read and Write access to code, merge queues and pull requests
# PERSONAL_ACCESS_TOKEN Actions secret should be added on organization level to be accesible by workflows in all repositories.
name: "CLA Assistant"
on:
workflow_call:
secrets:
personal_access_token:
required: true
# 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: read # 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/Netcracker/qubership-github-workflows/blob/main/CLA/cla.md'
# branch should not be protected
branch: 'main'
allowlist: bot*
remote-repository-name: cla-storage
remote-organization-name: Netcracker
# 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