name: "CLA Assistant"
on:
  issue_comment:
    types: [created]
  pull_request_target:
    types: [opened,closed,synchronize]

# Minimum scopes contributor-assistant/github-action needs to operate:
#   contents: write       - commit signatures to signatures/version1/cla.json
#   pull-requests: write  - comment on the PR with the CLA prompt
#   statuses: write       - set the commit status (success / pending)
# actions: write is intentionally NOT granted; this workflow does not manage
# other workflow runs.
permissions:
  contents: write
  pull-requests: write
  statuses: write

jobs:
  CLAAssistant:
    runs-on: ubuntu-latest
    steps:
      - name: "CLA Assistant"
        # Only run on pull_request_target events, or on issue_comment events
        # that are (a) on a PR (not a plain Issue) and (b) match one of the two
        # documented CLA phrases. github.event.issue.pull_request is truthy
        # only when the issue is a PR, so plain-Issue comments are ignored.
        if: |
          github.event_name == 'pull_request_target' ||
          (github.event_name == 'issue_comment' &&
           github.event.issue.pull_request != null &&
           (github.event.comment.body == 'recheck' ||
            github.event.comment.body == 'I have read the CLA Document and I hereby sign the CLA'))
        uses: contributor-assistant/github-action@ca4a40a7d1004f18d9960b404b97e5f30a505a08 # v2.6.1
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          # The below token is optional but recommended if the CLA signatures should be stored in a private repository or you want to trigger other workflows
          # PERSONAL_ACCESS_TOKEN: ${{ secrets.PERSONAL_ACCESS_TOKEN }}
        with:
          path-to-signatures: 'signatures/version1/cla.json'
          path-to-document: 'https://github.com/studio-saelix/sencho/blob/main/CLA.md'
          branch: 'main'
          allowlist: 'AnsoCode,dependabot[bot],greenkeeper[bot],github-actions[bot],release-please[bot],sencho-quartermaster[bot]'
          # Default true locks merged PR conversations, which blocks
          # release-please from commenting "included in vX.Y.Z" on the
          # release PR. Signatures live in signatures/version1/cla.json.
          lock-pullrequest-aftermerge: false