调用GitHub工作流时能否模拟GitHub上下文？求更优集成方案

无需修改现有BuildFlow，只需在ReleaseFlow中添加以下步骤即可满足需求：

• 安装GitHub CLI：在ReleaseFlow的作业环境中部署gh工具，用于触发和查询工作流状态
• 触发BuildFlow：通过gh workflow run命令调用BuildFlow，同时传递模拟release事件所需的上下文参数，让BuildFlow认为是原生release事件触发
• 等待工作流完成：通过gh run watch追踪BuildFlow的运行状态，确保ReleaseFlow能同步感知其结果

具体示例代码 #

jobs:
  trigger-and-monitor-build:
    runs-on: ubuntu-latest
    steps:
      - name: 安装GitHub CLI
        run: |
          type -p curl >/dev/null || (sudo apt update && sudo apt install curl -y)
          curl -fsSL https://cli.github.com/packages/githubcli-archive-keyring.gpg | sudo dd of=/usr/share/keyrings/githubcli-archive-keyring.gpg \
          && sudo chmod go+r /usr/share/keyrings/githubcli-archive-keyring.gpg \
          && echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/githubcli-archive-keyring.gpg] https://cli.github.com/packages stable main" | sudo tee /etc/apt/sources.list.d/github-cli.list > /dev/null \
          && sudo apt update && sudo apt install gh -y

      - name: 触发BuildFlow工作流
        id: trigger-build
        run: |
          WORKFLOW_RUN_ID=$(gh workflow run BuildFlow.yml \
            --ref ${{ github.ref }} \
            -f event_name=release \
            -f tag_name=${{ github.event.release.tag_name }} \
            --json id --jq '.id')
          echo "workflow_run_id=$WORKFLOW_RUN_ID" >> $GITHUB_OUTPUT
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

      - name: 等待BuildFlow执行完成
        run: |
          gh run watch ${{ steps.trigger-build.outputs.workflow_run_id }} --exit-status
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

方案优势 #

• 零修改BuildFlow：BuildFlow完全沿用原有对release事件的处理逻辑，传入的event_name参数会让它判定为原生release事件触发
• 全链路状态可见：GitHub GUI中可直接查看被触发的BuildFlow实例；ReleaseFlow通过gh run watch同步等待，BuildFlow的失败/成功状态会直接传递给ReleaseFlow
• 权限简洁：无需额外创建PAT，使用GitHub Actions默认的GITHUB_TOKEN即可完成触发和状态追踪

如果需要更精准的上下文模拟，可通过-f参数传递更多github.event.release下的字段（如release_name、draft等），让BuildFlow的执行逻辑与手动创建Release时完全一致。

内容的提问来源于stack exchange，提问作者Vitaly Karasik DevOps