heavy-duty/rig
7
0
Fork 1
Code Issues 10 Pull requests Projects Releases 3 Packages Wiki Activity Actions

docs: record the DEFAULT_ACTIONS_URL ruling
Some checks failed
ci / check (pull_request) Has been cancelled
Details
ci / install (pull_request) Has been cancelled
Details
ci / db-integration (pull_request) Has been cancelled
Details
labels / labels (pull_request) Has been cancelled
Details

Browse source 
The maintainer ruled on the conflict kimi found reviewing !110: keep
DEFAULT_ACTIONS_URL=https://code.forgejo.org — actions/* are exactly what that
setting is designed to resolve, and the mirror serves them — and make the eight
first-party ceremony references absolute instead.

The README stated the conflict but deliberately left the direction open. It now
names the ruling and shows the absolute form, and points at forgejo#112 where
the workflow edits are tracked. Those edits are not made here: they touch
release ceremony, and folding them into a PR three reviewers have already read
would invalidate those reviews for no benefit.

forgejo#109

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
cluade-reviewer-andresmgsl 2026-07-27 21:26:18 +00:00
parent cf5858bb60
commit 72ae875b90
1 changed files with 13 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
README.md
View file

@ -1188,13 +1188,19 @@ FORGEJO__actions__DEFAULT_ACTIONS_URL=https://code.forgejo.org
> `runner-isolated`, `docs-sync`, and the release/labels callers) fails to
> resolve the moment rig's CI actually runs on the forge.
>
> Forgejo accepts an absolute URL per step, so one side has to be explicit —
> which one is a **decision this PR does not make**. Either set the default to
> this instance and make the three `actions/*` references absolute
> (`uses: https://code.forgejo.org/actions/checkout@v4`), or keep the value
> above and make the eight ceremony references absolute. Until that lands,
> **rig's CI is not expected to run on Forgejo** — `rig forgejo-runner` is for
> running *your* repositories' workflows, and does not depend on this.
> Forgejo accepts an absolute URL per step, so one side has to be explicit.
> **The ruling is to keep the value above** — `actions/*` are exactly what
> `DEFAULT_ACTIONS_URL` is designed to resolve, and `code.forgejo.org` mirrors
> them — and to make the eight first-party references absolute:
>
> ```yaml
> - uses: https://forgejo.heavyduty.builders/heavy-duty/ceremony/actions/docs-sync@0.3.0
> ```
>
> That change is tracked in forgejo#112, not made here. Until it lands,
> **rig's own CI is not expected to run on Forgejo**.
> `rig forgejo-runner` exists to run *your repositories'* workflows and does not
> depend on any of it — the value above is correct for those from the start.
> **A registry served from Forgejo needs one more.** `RIG_TEMPLATES_HOST`
> (below) lets the template registry live on any forge, but the mint-time fetch