There are a few things happening here: - Rename the command dispatch release events to be prefixed with trigger- - Introduce a new command-dispatch event This new event listens for a trigger term in a comment e.g. /run-acceptance-tests This trigger term is *only* needed when the PR is from a fork! When the trigger term is posted then the run-build-and-acceptance-tests.yml event is fired - run-build-and-acceptance-tests.yml If the user runs the code from a pulumi based branch, then the tests and builds will work as normal If this file is being run via respository_dispatch then it will be able to run the test and builds and also post a comment back to the PR with the link to the test run It's important to say that PRs affecting the codegen and resource docs paths will only fire from a pulumi based branch - there is currently no command dispatch events for these codegen and resource PRs!
19 lines
549 B
YAML
19 lines
549 B
YAML
name: Command Dispatch for Running PR Acceptance Tests
|
|
on:
|
|
issue_comment:
|
|
types: [created, edited]
|
|
|
|
jobs:
|
|
command-dispatch-for-testing:
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- uses: actions/checkout@v2
|
|
- name: Run Build
|
|
uses: peter-evans/slash-command-dispatch@v2
|
|
with:
|
|
token: ${{ secrets.PULUMI_BOT_TOKEN }}
|
|
reaction-token: ${{ secrets.GITHUB_TOKEN }}
|
|
commands: run-acceptance-tests
|
|
permission: write
|
|
issue-type: pull-request
|
|
repository: pulumi/pulumi
|