1
0
mirror of https://github.com/kremalicious/metamask-extension.git synced 2024-11-30 08:09:15 +01:00
metamask-extension/.github/workflows/cla.yml
Mark Stacey fae857d1c0
Fix CLA Signature bot workflow (#11250)
In a recent PR (#11240) the workflow was updated to explicitly add the
required permissions. Unfortunately the "pull-requests" permission was
added with a space instead of a dash, which apparently breaks the
workflow. It now has a dash, as shown in the example in the docs [1].

[1]: https://docs.github.com/en/actions/reference/authentication-in-a-workflow#example-1-passing-the-github_token-as-an-input
2021-06-07 18:13:31 -02:30

28 lines
887 B
YAML

name: "CLA Signature Bot"
on:
issue_comment:
types: [created]
pull_request_target:
types: [opened,closed,synchronize]
jobs:
CLABot:
if: github.event_name == 'pull_request_target' || contains(github.event.comment.html_url, '/pull/')
runs-on: ubuntu-latest
permissions:
pull-requests: write
contents: write
steps:
- name: "CLA Signature Bot"
uses: MetaMask/cla-signature-bot@v3.0.2
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
with:
path-to-signatures: 'cla.json'
url-to-cladocument: 'https://metamask.io/cla.html'
# This branch can't have protections, commits are made directly to the specified branch.
branch: 'cla-signatures'
allowlist: 'dependabot[bot],metamaskbot'
allow-organization-members: true
blockchain-storage-flag: false