Skip to content

Commit

Permalink
ci: use different CLC checker action.
Browse files Browse the repository at this point in the history
  • Loading branch information
zicklag committed Jun 5, 2024
1 parent a583615 commit b04b2ab
Showing 1 changed file with 34 additions and 8 deletions.
42 changes: 34 additions & 8 deletions .github/workflows/check-for-clc.yaml
Original file line number Diff line number Diff line change
@@ -1,14 +1,40 @@
name: Check for CLC Confirmation
name: "CLC Assistant"
on:
pull_request:
types: [opened, synchronize, edited]
issue_comment:
types: [created]
pull_request_target:
types: [opened,closed,synchronize]

env:
checkbox: "I have read and agree with the [Contributor License Compromise](https://github.com/commune-os/weird/blob/main/CONTRIBUTING.md#contributor-license-compromise)."
# explicitly configure permissions, in case your GITHUB_TOKEN workflow permissions are set to read-only in repository settings
permissions:
actions: write
contents: write # this can be 'read' if the signatures are in remote repository
pull-requests: write
statuses: write

jobs:
check_pull_request:
CLCAssistant:
runs-on: ubuntu-latest
steps:
- name: Validate
uses: MatiBrond/github-actions-checkbox-check@0.0.2
- name: "CLA Assistant"
if: (github.event.comment.body == 'recheck' || github.event.comment.body == 'I have read the CLC Document and I hereby sign the CLC') || github.event_name == 'pull_request_target'
uses: contributor-assistant/github-action@v2.4.0
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
with:
path-to-signatures: 'signatures/version1/cla.json'
path-to-document: 'https://github.com/commune-os/weird/blob/a583615a9d34d913f5e63065768cdbe02750ae43/CONTRIBUTING.md' # e.g. a CLA or a DCO document
# branch should not be protected
branch: 'clc-signatures'
allowlist: zicklag,erlend-sh,hnb-ku

# 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

0 comments on commit b04b2ab

Please sign in to comment.