8396030578
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!
30 lines
754 B
YAML
30 lines
754 B
YAML
env:
|
|
GITHUB_TOKEN: ${{ secrets.PULUMI_BOT_TOKEN }}
|
|
VERSION: ${{ github.event.client_payload.ref }}
|
|
COMMIT_SHA: ${{ github.event.client_payload.commitSha }}
|
|
|
|
on:
|
|
repository_dispatch:
|
|
types:
|
|
- docs
|
|
|
|
jobs:
|
|
docs:
|
|
name: Build Package Docs
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- name: Checkout
|
|
uses: actions/checkout@v2
|
|
- name: Checkout Scripts Repo
|
|
uses: actions/checkout@v2
|
|
with:
|
|
path: ci-scripts
|
|
repository: pulumi/scripts
|
|
- name: Trigger Docs Build
|
|
run: |
|
|
./ci-scripts/ci/build-package-docs.sh "pulumi"
|
|
env:
|
|
TRAVIS: true
|
|
PULUMI_BOT_GITHUB_API_TOKEN: ${{ secrets.PULUMI_BOT_TOKEN }}
|
|
TRAVIS_TAG: ${{ env.VERSION }}
|