e33a887055
* Add CLA github action * Change license to AGPLv3
36 lines
1.9 KiB
YAML
36 lines
1.9 KiB
YAML
name: 'CLA Assistant'
|
|
on:
|
|
issue_comment:
|
|
types: [created]
|
|
pull_request_target:
|
|
types: [opened, closed, synchronize]
|
|
|
|
jobs:
|
|
CLAssistant:
|
|
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'
|
|
# Beta Release
|
|
uses: cla-assistant/github-action@v2.2.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
|
|
PERSONAL_ACCESS_TOKEN: ${{ secrets.CLA_PAT }}
|
|
with:
|
|
path-to-signatures: 'signatures.json'
|
|
path-to-document: 'https://github.com/cinnyapp/cla/blob/main/cla.md' # e.g. a CLA or a DCO document
|
|
# branch should not be protected
|
|
branch: 'main'
|
|
allowlist: ajbura,bot*
|
|
|
|
#below are the optional inputs - If the optional inputs are not given, then default values will be taken
|
|
remote-organization-name: cinnyapp
|
|
remote-repository-name: cla
|
|
#create-file-commit-message: 'For example: Creating file for storing CLA Signatures'
|
|
#signed-commit-message: 'For example: $contributorName has signed the CLA in #$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
|