## Description Bumps ok-to-test to v3. Plus fix the issue where someone might have been able to run unverified code if they push between commenting `/ok-to-test` and the job starting. ## Type of change <!--- Please check the type of change your PR introduces: ---> - [ ] 🌻 Feature - [ ] 🐛 Bugfix - [ ] 🗺️ Documentation - [ ] 🤖 Test - [x] 💻 CI/Deployment - [ ] 🐹 Trivial/Minor ## Issue(s) <!-- Can reference multiple issues. Use one of the following "magic words" - "closes, fixes" to auto-close the Github issue. --> * https://github.com/alcionai/corso/pull/1651 ## Test Plan <!-- How will this be tested prior to merging.--> - [x] 💪 Manual - [ ] ⚡ Unit test - [ ] 💚 E2E
31 lines
913 B
YAML
31 lines
913 B
YAML
# If someone with write access comments "/ok-to-test" on a pull request, emit a repository_dispatch event
|
|
name: Ok To Test
|
|
|
|
on:
|
|
issue_comment:
|
|
types: [created]
|
|
|
|
jobs:
|
|
ok-to-test:
|
|
runs-on: ubuntu-latest
|
|
# Only run for PRs, not issue comments
|
|
if: ${{ github.event.issue.pull_request }}
|
|
steps:
|
|
- name: Generate token
|
|
id: generate_token
|
|
uses: tibdex/github-app-token@v1
|
|
with:
|
|
app_id: ${{ secrets.APP_ID }}
|
|
private_key: ${{ secrets.PRIVATE_KEY }}
|
|
|
|
- name: Slash Command Dispatch
|
|
uses: peter-evans/slash-command-dispatch@v3
|
|
env:
|
|
TOKEN: ${{ steps.generate_token.outputs.token }}
|
|
with:
|
|
token: ${{ env.TOKEN }} # GitHub App installation access token
|
|
reaction-token: ${{ secrets.GITHUB_TOKEN }}
|
|
issue-type: pull-request
|
|
commands: ok-to-test
|
|
permission: write
|