如何针对外部协作者跳过GitHub端到端测试工作流？

要实现直接跳过整个工作流（而非仅测试步骤），可以通过在GitHub Workflow的job级别或触发规则（on）级别添加条件判断，精准识别外部协作者的PR并跳过执行。以下是三种实用方案：

方案一：基于仓库密钥存在性判断（复用现有逻辑） #

利用外部PR中仓库密钥会被自动置空的特性，给整个test job添加执行条件，密钥不存在时直接跳过整个job：

name: "E2E Tests"
on:
  push:
    branches: [master]
  pull_request:
    branches: [master]
jobs:
  test:
    runs-on: ubuntu-latest
    # 仅当SECRETS_SET密钥存在时，才执行整个job
    if: ${{ secrets.SECRETS_SET != '' }}
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: 18
      - name: Install dependencies
        run: yarn install
      - name: Install Playwright Browsers
        run: npx playwright install --with-deps
      - name: Run Playwright tests
        run: yarn test:e2e

方案二：基于PR来源仓库判断（无需额外密钥） #

通过GitHub上下文对比PR的源仓库与当前仓库，判断是否为外部协作者提交的PR，逻辑更精准且无需依赖额外密钥：

name: "E2E Tests"
on:
  push:
    branches: [master]
  pull_request:
    branches: [master]
jobs:
  test:
    runs-on: ubuntu-latest
    # 仅当是push到master，或是内部仓库发起的PR时执行
    if: ${{ github.event_name == 'push' || github.event.pull_request.head.repo.full_name == github.repository }}
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: 18
      - name: Install dependencies
        run: yarn install
      - name: Install Playwright Browsers
        run: npx playwright install --with-deps
      - name: Run Playwright tests
        run: yarn test:e2e

方案三：在触发规则层面直接过滤（完全不触发工作流） #

如果希望外部协作者的PR完全不触发该工作流（连工作流记录都不生成），可以在pull_request的触发规则里添加条件：

name: "E2E Tests"
on:
  push:
    branches: [master]
  pull_request:
    branches: [master]
    # 仅允许内部仓库发起的PR触发工作流
    if: ${{ github.event.pull_request.head.repo.full_name == github.repository }}
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: 18
      - name: Install dependencies
        run: yarn install
      - name: Install Playwright Browsers
        run: npx playwright install --with-deps
      - name: Run Playwright tests
        run: yarn test:e2e

方案选择建议 #

• 若需要保留工作流记录但跳过执行：选方案一或方案二；
• 若完全不想让外部PR触发工作流：选方案三；
• 优先推荐方案二，无需额外维护密钥，逻辑更清晰。

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