.github/workflows/check-cla.yml - main - githubmirror/serverless

.github/workflows/check-cla.yml
45 строк3 KB
Tomasz Czubocha
chore(ci): update CLA allowlist (#13295)
26 янв 2026, 20:43
26 янв 2026, 20:4373f57b4
name: 'Check: Contributor License Agreement'

# 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

on:
  issue_comment:
    types: [created]
  pull_request_target:
    types: [opened, closed, synchronize]

jobs:
  check-cla-signature:
    name: 'Check: CLA Signature'
    runs-on: ubuntu-latest
    steps:
      - name: 'Verify Signature'
        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@ca4a40a7d1004f18d9960b404b97e5f30a505a08 # 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.CLA_PERSONAL_ACCESS_TOKEN }}
        with:
          path-to-signatures: 'signatures/version1/cla.json'
          path-to-document: 'https://github.com/serverless/serverless/blob/main/CLA.md' # e.g. a CLA or a DCO document
          # branch should not be protected
          branch: 'main'
          allowlist: czubocha,eahefnawy,austencollins,Mmarzex,skierkowski,dependabot[bot],snyk-bot,aikido-autofix[bot],coderabbitai[bot],cursoragent

          # the followings are the optional inputs - If the optional inputs are not given, then default values will be taken
          remote-organization-name: serverlessinc # enter the remote organization name where the signatures should be stored (Default is storing the signatures in the same repository)
          remote-repository-name: cla # 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