如何配置GitHub Actions在Pull Request所有状态检查完成时触发？

问题分析 #

直接使用status或check_run触发器时，GitHub Actions不会自动关联Pull Request的状态检查完成事件——这两个触发器的默认触发条件过于宽泛，且未明确针对PR的检查完成状态做约束，导致无法精准触发。

可行配置方案 #

方案1：用pull_request_target配合检查等待动作 #

这种方式能精准监听PR的必填状态检查完成且通过的事件：

name: Run integration tests
run-name: Run integration tests
on:
  pull_request_target:
    types: [opened, synchronize, reopened]
    branches: [main] # 替换为你的目标分支名称

jobs:
  wait-for-required-checks:
    runs-on: ubuntu-latest
    outputs:
      checks_passed: ${{ steps.check-status.outputs.checks_passed }}
    steps:
      - name: 等待必填状态检查通过
        id: check-status
        uses: lewagon/wait-on-check-action@v1.3.0
        with:
          ref: ${{ github.event.pull_request.head.sha }}
          check-name: "第三方CI检查名称" # 替换为你的第三方CI工具的检查名称，多个用逗号分隔
          repo-token: ${{ secrets.GITHUB_TOKEN }}
          wait-interval: 30
          allowed-conclusions: success

  deploy-to-integration:
    needs: wait-for-required-checks
    if: ${{ needs.wait-for-required-checks.outputs.checks_passed == 'true' }}
    uses: ./.github/workflows/deploy-workflow.yml
    with:
      deployment_arguments: ...
    secrets: inherit

方案2：直接监听check_suite完成事件 #

如果第三方CI的检查是以检查套件形式运行的，可使用这个触发器：

name: Run integration tests
run-name: Run integration tests
on:
  check_suite:
    types: [completed]
    branches: [main] # 目标分支

jobs:
  deploy-to-integration:
    if: ${{ github.event.check_suite.conclusion == 'success' && github.event.check_suite.pull_requests != [] }}
    uses: ./.github/workflows/deploy-workflow.yml
    with:
      deployment_arguments: ...
    secrets: inherit

方案3：修正check_run触发器配置 #

如果坚持用check_run，需补充触发类型和条件判断：

name: Run integration tests
run-name: Run integration tests
on:
  check_run:
    types: [completed]

jobs:
  deploy-to-integration:
    if: ${{ github.event.check_run.conclusion == 'success' && github.event.check_run.pull_requests != [] }}
    uses: ./.github/workflows/deploy-workflow.yml
    with:
      deployment_arguments: ...
    secrets: inherit

关键注意事项 #

• status触发器针对的是仓库全局状态，而非特定PR的检查完成，不适合用来监听PR的状态检查事件。
• 默认的GITHUB_TOKEN已具备读取检查状态的权限，无需额外配置权限。

内容的提问来源于stack exchange，提问作者Matt C