Skip to content

Commit

Permalink
Merge pull request #500 from mlcommons/update-cla-bot-2022
Browse files Browse the repository at this point in the history
Update CLA bot
  • Loading branch information
TheKanter authored Aug 11, 2022
2 parents 7a95b01 + 8ac4dab commit 5a91000
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions .github/workflows/cla.yml
Original file line number Diff line number Diff line change
@@ -1,3 +1,4 @@

name: "cla-bot"
on:
issue_comment:
Expand All @@ -12,20 +13,19 @@ jobs:
- name: "MLCommons CLA bot check"
if: (github.event.comment.body == 'recheck') || github.event_name == 'pull_request_target'
# Alpha Release
uses: sub-mod/github-action@v3
uses: mlcommons/cla-bot@master
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
PERSONAL_ACCESS_TOKEN : ${{ secrets.MLCOMMONS_BOT_CLA_TOKEN }}
with:
path-to-signatures: 'cla-bot/v1/cla.json'
path-to-document: 'https://github.com/mlcommons/systems/blob/main/mlcommons_cla.txt' # e.g. a CLA or a DCO document
# branch should not be protected
branch: 'main'
allowlist: user1,bot*
remote-organization-name: mlcommons
remote-repository-name: systems

#below 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)
Expand Down

0 comments on commit 5a91000

Please sign in to comment.