bvandeusen/FabledSteward
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

docs: Fabled-Git, not Forgejo, in ci-requirements
CI / lint (push) Successful in 3s
Details
CI / unit (push) Successful in 49s
Details
CI / integration (push) Successful in 2m30s
Details
CI / publish (push) Successful in 1m27s
Details

Browse Source 
The instance has run Gitea since the migration; "Forgejo Actions services:"
is Fabled-Git Actions. Prose only — no workflow or path change.
Scribe issue #2272.
This commit is contained in:
bvandeusen
2026-07-31 23:42:38 -04:00
parent 8c2d994e4c
commit 4b97bd01ea
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
ci-requirements.md
+1 -1
View File
@@ -46,7 +46,7 @@ git.fabledsword.com/bvandeusen/ci-python:3.14
- Steward has **no frontend and no Redis/Celery** (no external workers), so there
is no frontend-build lane and the only service container is Postgres.
- Integration uses Forgejo Actions `services:` + a socket-discovered bridge IP
- Integration uses Fabled-Git Actions `services:` + a socket-discovered bridge IP
because `act_runner` (swarm-runner v0.6+) puts services on the default bridge
with no embedded DNS. FabledCurator's `ci.yml` is the canonical example of the
pattern; Steward's is the same shape minus Redis and minus sharding.