fix: bump vllm-router image to nightly-20260708-b93cbcb / 升级 vllm-router 镜像至 nightly-20260708-b93cbcb #4107
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| name: PR Recipe Reminder | |
| on: | |
| pull_request: | |
| types: [opened, reopened, ready_for_review, review_requested] | |
| paths: | |
| - 'configs/amd-master.yaml' | |
| - 'configs/nvidia-master.yaml' | |
| - 'benchmarks/**' | |
| - 'perf-changelog.yaml' | |
| permissions: | |
| pull-requests: write | |
| jobs: | |
| comment: | |
| runs-on: ubuntu-latest | |
| steps: | |
| - name: Comment recipe reminder | |
| uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0 | |
| with: | |
| script: | | |
| const owner = context.repo.owner; | |
| const repo = context.repo.repo; | |
| const issue_number = context.payload.pull_request.number; | |
| // Check if we already left this comment to avoid duplicates | |
| const comments = await github.rest.issues.listComments({ owner, repo, issue_number }); | |
| const marker = '<!-- recipe-reminder -->'; | |
| const alreadyCommented = comments.data.some(c => c.body.includes(marker)); | |
| if (alreadyCommented) { | |
| core.info('Recipe reminder already posted, skipping.'); | |
| return; | |
| } | |
| const body = `${marker} | |
| Thanks for the contribution! Please reach out to respective companies' [CODEOWNER](https://github.com/SemiAnalysisAI/InferenceX/blob/main/.github/CODEOWNERS) to fill in the latest [PR_REVIEW_CHECKLIST.md](https://github.com/SemiAnalysisAI/InferenceX/blob/main/docs/PR_REVIEW_CHECKLIST.md) before pinging core maintainer on Slack for review. In order for the signoff PR check bot to trigger, you must follow the PR_REVIEW_CHECKLIST.md template correctly, including the phrase \`As a PR reviewer and CODEOWNER, I have reviewed this and have\`. | |
| For PR verification, add the \`full-sweep-fail-fast\` label (strongly recommended) to this PR — the benchmark sweep only runs on labeled PRs. Use \`full-sweep-enabled\` only if you need matrix jobs to keep running past a failure. | |
| **PR authors are responsible for ensuring that after merging, all GitHub Action jobs fully pass.** A lot of the time, failures are just flakes and simply re-running the failed jobs will fix it. [See GitHub's docs on re-running failed jobs](https://docs.github.com/en/actions/how-tos/manage-workflow-runs/re-run-workflows-and-jobs#re-running-failed-jobs-in-a-workflow) | |
| --- | |
| 感谢你的贡献！请联系相应公司的 [CODEOWNER](https://github.com/SemiAnalysisAI/InferenceX/blob/main/.github/CODEOWNERS) 填写最新的 [PR_REVIEW_CHECKLIST.md](https://github.com/SemiAnalysisAI/InferenceX/blob/main/docs/PR_REVIEW_CHECKLIST.md)，然后再在 Slack 上联系核心维护者进行审阅。为了触发 signoff PR 检查机器人，你必须正确遵循 PR_REVIEW_CHECKLIST.md 模板，包括保留英文语句 \`As a PR reviewer and CODEOWNER, I have reviewed this and have\`。 | |
| 如需进行 PR 验证，请为此 PR 添加 \`full-sweep-fail-fast\` 标签（强烈推荐）— 基准测试 sweep 仅在带有标签的 PR 上运行。仅当需要矩阵任务在失败后继续运行时才使用 \`full-sweep-enabled\`。 | |
| **PR 作者有责任确保合并后所有 GitHub Action 任务完全通过。** 很多时候失败只是偶发抖动（flake），重新运行失败的任务即可解决。[参见 GitHub 关于重新运行失败任务的文档](https://docs.github.com/en/actions/how-tos/manage-workflow-runs/re-run-workflows-and-jobs#re-running-failed-jobs-in-a-workflow)`.replace(/^ /gm, ''); | |
| await github.rest.issues.createComment({ owner, repo, issue_number, body }); |