Skip to content

CI: update libfabric to 1.22.0 #843

CI: update libfabric to 1.22.0

CI: update libfabric to 1.22.0 #843

Workflow file for this run

name: "CLA Assistant"
on:
issue_comment:
types: [created]
pull_request_target:
types: [opened,closed,synchronize]
jobs:
pr_commented:
runs-on: ubuntu-latest
steps:
- name: "CLA Assistant"
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'
# Beta Release
uses: contributor-assistant/github-action@v2.2.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
PERSONAL_ACCESS_TOKEN : ${{ secrets.CLA_ASSISTANT_TOKEN }}
with:
path-to-signatures: 'digital/cla.json'
path-to-document: 'https://mercury-hpc.github.io/assets/CLA/mercury-cla-individual-2021-07.pdf' # e.g. a CLA or a DCO document
# branch should not be protected
branch: 'main'
allowlist: bot*
#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-organization-name: 'mercury-hpc'
#remote-repository-name: enter the remote repository name where the signatures should be stored (Default is storing the signatures in the same repository)
remote-repository-name: 'mercury-cla'
#create-file-commit-message: 'For example: Creating file for storing CLA Signatures'
#signed-commit-message: 'For example: $contributorName has signed the CLA in #$pullRequestNo'
#custom-notsigned-prcomment: 'pull request comment with Introductory message to ask new contributors to sign'
custom-notsigned-prcomment: 'Thank you for your contribution! Before this PR can be accepted, we require that you read and agree to the Mercury [Contributor License Agreement](https://mercury-hpc.github.io/assets/CLA/mercury-cla-individual-2021-07.pdf). You can digitally sign the CLA by posting a comment on this Pull Request in the format shown below. This agreement will apply to this PR as well as all future Mercury contributions.<br /><br />For more information, or instructions on how to sign an institution-level CLA, please see the [Contribute](https://mercury-hpc.github.io/help/#contribute) page.'
#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