cla.yml 2.7 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243
  1. name: "MinerU CLA Assistant"
  2. on:
  3. issue_comment:
  4. types: [created]
  5. pull_request_target:
  6. types: [opened,closed,synchronize]
  7. # explicitly configure permissions, in case your GITHUB_TOKEN workflow permissions are set to read-only in repository settings
  8. permissions:
  9. actions: write
  10. contents: write # this can be 'read' if the signatures are in remote repository
  11. pull-requests: write
  12. statuses: write
  13. jobs:
  14. CLAAssistant:
  15. runs-on: ubuntu-latest
  16. steps:
  17. - name: "CLA Assistant"
  18. 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'
  19. uses: contributor-assistant/github-action@v2.5.0
  20. env:
  21. GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
  22. # the below token should have repo scope and must be manually added by you in the repository's secret
  23. # This token is required only if you have configured to store the signatures in a remote repository/organization
  24. PERSONAL_ACCESS_TOKEN: ${{ secrets.RELEASE_TOKEN }}
  25. with:
  26. path-to-signatures: 'signatures/version1/cla.json'
  27. path-to-document: 'https://github.com/opendatalab/MinerU/blob/master/MinerU_CLA.md' # e.g. a CLA or a DCO document
  28. # branch should not be protected
  29. branch: 'master'
  30. allowlist: myhloli,dt-yy,Focusshang,renpengli01,icecraft,drunkpig,wangbinDL,qiangqiang199,GDDGCZ518,papayalove,conghui,quyuan,LollipopsAndWine
  31. # the followings are the optional inputs - If the optional inputs are not given, then default values will be taken
  32. #remote-organization-name: enter the remote organization name where the signatures should be stored (Default is storing the signatures in the same repository)
  33. #remote-repository-name: enter the remote repository name where the signatures should be stored (Default is storing the signatures in the same repository)
  34. #create-file-commit-message: 'For example: Creating file for storing CLA Signatures'
  35. #signed-commit-message: 'For example: $contributorName has signed the CLA in $owner/$repo#$pullRequestNo'
  36. #custom-notsigned-prcomment: 'pull request comment with Introductory message to ask new contributors to sign'
  37. #custom-pr-sign-comment: 'The signature to be committed in order to sign the CLA'
  38. #custom-allsigned-prcomment: 'pull request comment when all contributors has signed, defaults to **CLA Assistant Lite bot** All Contributors have signed the CLA.'
  39. #lock-pullrequest-aftermerge: false - if you don't want this bot to automatically lock the pull request after merging (default - true)
  40. #use-dco-flag: true - If you are using DCO instead of CLA