Skip to content

test(core): add unit tests for customer-group promotion condition #11481

test(core): add unit tests for customer-group promotion condition

test(core): add unit tests for customer-group promotion condition #11481

Workflow file for this run

name: "CLA Assistant"
on:
issue_comment:
types: [created]
pull_request_target:
types: [opened,closed,synchronize]
# explicitly configure permissions, in case your GITHUB_TOKEN workflow permissions are set to read-only in repository settings
permissions:
actions: write
contents: write # this can be 'read' if the signatures are in remote repository
pull-requests: write
statuses: write
jobs:
CLAAssistant:
runs-on: ubuntu-latest
steps:
- name: Generate CI Bot Token
id: app-token
uses: actions/create-github-app-token@fee1f7d63c2ff003460e3d139729b119787bc349 # v2.2.2
with:
app-id: ${{ secrets.CI_BOT_APP_ID }}
private-key: ${{ secrets.CI_BOT_APP_PRIVATE_KEY }}
# Least privilege: the CLA assistant stores signatures (contents), comments on PRs
# (pull-requests), and sets the CLA commit status that gates merge (statuses).
# NOTE: we do NOT request `actions: write` — the vendure-ci-automation-bot App only
# grants `actions: read`, and requesting a permission the App lacks hard-fails token
# creation. It isn't needed anyway: the "recheck" flow is driven by the issue_comment
# trigger (a new event re-runs this workflow), not by an API workflow re-run.
permission-contents: write
permission-pull-requests: write
permission-statuses: write
# Third-party actions are pinned to commit SHAs to prevent supply chain attacks
# via mutable version tags. See https://docs.github.com/en/actions/security-for-github-actions/security-guides/security-hardening-for-github-actions#using-third-party-actions
- 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'
uses: contributor-assistant/github-action@9340315624c6e16cef1f2c63bdeb0f0c49c6f474 # v2.4.0
env:
GITHUB_TOKEN: ${{ steps.app-token.outputs.token }}
with:
path-to-signatures: 'license/signatures/version1/cla.json'
path-to-document: 'https://github.com/vendurehq/vendure/blob/master/license/CLA.md'
branch: 'master'
allowlist: user1,bot*
# the followings 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)
#create-file-commit-message: 'For example: Creating file for storing CLA Signatures'
#signed-commit-message: 'For example: $contributorName has signed the CLA in $owner/$repo#$pullRequestNo'
#custom-notsigned-prcomment: 'pull request comment with Introductory message to ask new contributors to sign'
#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.'