Chinesezjc
1d5e4199c8
Per review on PR #2768: - Restore a concurrency block in ci.yml (cancel-in-progress: true) so a fresh PR push cancels the superseded run; GitHub has no default PR auto-cancel, so removing it would stack a second full 9-job run on every push. Update the ci-workflow.spec assertion accordingly. - Fix comment misplacements from the split boundary: ci.yml's all-checks-passed now carries its own branch-protection comment (the drill comment that was orphaned above it is gone), and ci-master.yml no longer ends with an orphaned all-checks-passed comment. - Restore the DeepSeek e2e workflow describe-block in ci-workflow.spec.ts that the rewrite had silently deleted (e2e.yml is unchanged). - serial-windows comment no longer claims non-blocking-for-PR/absent-from-needs since ci-master never listens to pull_request. - DSH_TELEMETRY_DISABLED safe-use comment restored in ci-master.yml env; split rationale (mi gray segments in PR check) documented in .github/AGENTS.md. Verification: ci-workflow.spec.ts 13/13, both workflows YAML-parse with correct concurrency, git diff --check clean.
1.1 KiB
AGENTS.md — GitHub Actions
Run jobs on Windows runners (windows-* labels) under native pwsh. The pull-request windows job is the deliberate exception: it runs Windows Node under Wine on hosted Linux and blocks all checks passed; windows-native runs automatically on windows-2025 (or the self-hosted [self-hosted, dsh-win-ci, windows] pool under DSH_CI_FAILOVER_WINDOWS=selfhosted) but reports independently. ci.yml is pull-request-only; the master serial-windows standby, the Linux serial-linux-selfhosted standby, the wine-apt-cache seeder, and the two manual runner benchmarks live in ci-master.yml (master-push + workflow_dispatch). Because ci-master.yml does not listen to pull_request, those master-only jobs never appear in PR check panels (a job a workflow defines for a given event is listed and shows skipped when its if is false); keeping them in a separate workflow is what stops PR check circles from showing gray segments. The master serial-windows standby continuously validates the self-hosted failover target — see the failover runbook.