docs: sort the top-level directories into five sections by what the reader wants
Every docs directory moves under 1-getting-started, 2-handbook, 4-implementation or 5-project; the options reference (section 3) comes from the website and has no directory here. trust-boundary stays whole under the handbook for now. web-ui, swarm and tools split between handbook and implementation, and the command-line references move to 2-handbook/reference. Links, path references in code and nix, and the docs index follow the moves; no page content changes.
This commit is contained in:
parent
53ccbcb4b3
commit
6739bb903d
1 changed files with 736 additions and 701 deletions
|
|
@ -1,6 +1,6 @@
|
|||
//! OTEL export of commit/push activity across every forge repo in the
|
||||
//! instance — the metric forgejo's own native `/metrics` endpoint (see
|
||||
//! `docs/integrations/forge.md`'s note on the survey that shipped it) does not carry.
|
||||
//! `docs/2-handbook/integrations/forge.md`'s note on the survey that shipped it) does not carry.
|
||||
//! That endpoint gives issue/comment/repo counts because Forgejo tracks
|
||||
//! those as durable rows it can `SELECT COUNT(*)` on demand; a commit or a
|
||||
//! push is not stored anywhere as a row to count, only observed in passing
|
||||
|
|
|
|||
Loading…
Reference in a new issue