docs: the repo's own CI checks move from the CI runner page to the project process docs
docs/4-implementation/scheduler/ci.md described both the swarm-ci-runner product (hosting, registration, security, store maintenance) and this repo's own pipeline (which jobs run on a PR, the local equivalents, the nightly VM tests). The second part is project process: it moves, whole and in order, to docs/5-project/process/ci-checks.md, with a pointer left behind, an entry in the docs index and the one doc comment in hive-forge that named the old section updated.
This commit is contained in:
parent
f29435fcf1
commit
a19745d30d
1 changed files with 124 additions and 109 deletions
|
|
@ -149,7 +149,7 @@ Nothing of it sits in this tree.
|
|||
[`4-implementation/scheduler/jobq.md`](4-implementation/scheduler/jobq.md) — operator-facing, no implementation detail.
|
||||
- **How does the rebuild queue work? What are the concrete step kinds,
|
||||
queue sources, scheduler internals?** → [`4-implementation/scheduler/coordinator.md`](4-implementation/scheduler/coordinator.md).
|
||||
- **How does the CI runner work? How does it register?** →
|
||||
- **How does the CI runner work? How does it register? How's it hosted?** →
|
||||
[`4-implementation/scheduler/ci.md`](4-implementation/scheduler/ci.md).
|
||||
- **How are Claude Code metrics (tokens, cost, tool calls) exported to
|
||||
Prometheus/Grafana?** → [`4-implementation/scheduler/observability.md`](4-implementation/scheduler/observability.md).
|
||||
|
|
@ -229,6 +229,9 @@ How the project itself works: processes, conventions, design guides.
|
|||
[`5-project/process/conventions.md`](5-project/process/conventions.md).
|
||||
- **Why does the nspawn flag look like that?** → [`5-project/process/gotchas.md`](5-project/process/gotchas.md)
|
||||
(bind mounts, conf flags, other NixOS/nspawn quirks).
|
||||
- **Which checks run on a PR to this repo, and how do I run them before I push?** →
|
||||
[`5-project/process/ci-checks.md`](5-project/process/ci-checks.md) (the jobs, the local
|
||||
equivalents, the nightly VM tests).
|
||||
- **What does a PR review verdict actually gate?** →
|
||||
[`5-project/process/pr-review-gate.md`](5-project/process/pr-review-gate.md).
|
||||
- **How are the web UIs designed to look and behave?** →
|
||||
|
|
|
|||
Loading…
Reference in a new issue