From c2d27d9a2b55876e92330197bf2b84b66a634ab6 Mon Sep 17 00:00:00 2001 From: Bryan Van Deusen Date: Sat, 1 Aug 2026 19:54:43 -0400 Subject: [PATCH] docs(ci): name the service Fabled-Git, not Forgejo This instance runs Gitea 1.26.4. Per the naming decision on Scribe #2272, "Fabled-Git" is the standing name for the service and the engine is named only where it is load-bearing (version-specific API behaviour, act_runner quirks, click-through UI). Service-level prose only. Deliberately NOT touched: - `.forgejo/workflows/` paths, which resolve on this Gitea only because GITEA__actions__WORKFLOW_DIRS lists them. - anything naming the upstream Forgejo PROJECT (the artifact-action forks). Co-Authored-By: Claude Opus 5 (1M context) --- ci-requirements.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ci-requirements.md b/ci-requirements.md index 261cd9b..a7a2543 100644 --- a/ci-requirements.md +++ b/ci-requirements.md @@ -47,6 +47,6 @@ Friction, expectations, and anything the maintainer wouldn't see otherwise: compose pull). - Unit suite is a starter set covering the pure logic (hashing, SQLite dedup, media-extension filter, file transfer modes). Grow it as behavior is added. -- Requires repo Actions secret **`REGISTRY_TOKEN`** (Forgejo PAT, +- Requires repo Actions secret **`REGISTRY_TOKEN`** (Fabled-Git PAT, `read:package` + `write:package`) for the publish lane — the injected `GITHUB_TOKEN` can't push to the registry (family rule 7). -- 2.54.0