docs(ci): name the service Fabled-Git, not Forgejo #2

Merged
bvandeusen merged 1 commits from dev into main 2026-08-02 20:28:54 -04:00
Owner

One docs-only commit to ci-requirements.md.

Naming per Scribe #2272: git.fabledsword.com runs Gitea 1.26.4, not Forgejo. "Fabled-Git" is the standing name for the service; the engine is named only where it's load-bearing.

One change — the REGISTRY_TOKEN note:

-- Requires repo Actions secret **`REGISTRY_TOKEN`** (Forgejo PAT,
+- Requires repo Actions secret **`REGISTRY_TOKEN`** (Fabled-Git PAT,

The surrounding detail stays exactly as-is: read:package + write:package scopes, and the reason the injected GITHUB_TOKEN can't push to the registry (family rule 7). Those are engine-accurate and load-bearing.

Verified before opening: ci-requirements.md is byte-identical between main and this commit's parent, so the merge applies cleanly.

🤖 Generated with Claude Code

One docs-only commit to `ci-requirements.md`. Naming per Scribe #2272: `git.fabledsword.com` runs **Gitea 1.26.4**, not Forgejo. "Fabled-Git" is the standing name for the service; the engine is named only where it's load-bearing. One change — the `REGISTRY_TOKEN` note: ```diff -- Requires repo Actions secret **`REGISTRY_TOKEN`** (Forgejo PAT, +- Requires repo Actions secret **`REGISTRY_TOKEN`** (Fabled-Git PAT, ``` The surrounding detail stays exactly as-is: `read:package` + `write:package` scopes, and the reason the injected `GITHUB_TOKEN` can't push to the registry (family rule 7). Those are engine-accurate and load-bearing. Verified before opening: `ci-requirements.md` is byte-identical between `main` and this commit's parent, so the merge applies cleanly. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
bvandeusen added 1 commit 2026-08-01 22:23:24 -04:00
docs(ci): name the service Fabled-Git, not Forgejo
CI / lint (push) Successful in 3s
CI / unit (push) Successful in 5s
CI / publish (push) Successful in 13s
c2d27d9a2b
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) <noreply@anthropic.com>
bvandeusen merged commit fa97a68844 into main 2026-08-02 20:28:54 -04:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bvandeusen/StashHandler#2