deepseek-harness/.github/workflows
Chinesezjc ce3b13bb08 ci: standby fetches full history; runbook — writer wording throughout, master-ref pinning incompatibility
- serial-linux-selfhosted checks out fetch-depth 0: depth 2 misses
  github.event.before on multi-commit or force pushes, failing the
  archive verifier on a valid tree. Full fetch is cheap against the
  VM's local mirror.
- Runbook (both languages): every remaining admin phrasing (problem
  statement, switch heading, alternatives, consequences) now says
  writer; and the 'composes with this mechanism' claim about a
  master-ref-pinned runner group is replaced with the truth observed
  live on 2026-07-27 — master-ref pinning blocks PR failover, and the
  shipped posture is repository-scoped all-workflow group access.
Static gate green locally: 32 passed, 0 failed.
2026-07-27 16:13:45 +08:00
..
build-exe-for-python-sdk.yml Rename RFCs to Agent Notes 2026-07-19 22:52:03 +08:00
ci.yml ci: standby fetches full history; runbook — writer wording throughout, master-ref pinning incompatibility 2026-07-27 16:13:45 +08:00
docs-pages.yml ci: restrict Pages deployment to master 2026-07-20 18:41:10 +08:00
e2e.yml Rename RFCs to Agent Notes 2026-07-19 22:52:03 +08:00
expected-filenames.yml ci: reject golden filenames on matching PRs 2026-07-19 21:24:42 +08:00
landlock-run.yml chore: adopt node-addon-landlock-run source as native/ subtree 2026-07-14 23:39:58 +08:00
pi-ai-provider-e2e.yml fix(ci): target Azure Foundry OpenAI v1 route 2026-07-19 14:06:18 +08:00
sandbox.yml Rename RFCs to Agent Notes 2026-07-19 22:52:03 +08:00