README's install quick start has no Forgejo channel — RIG_HOST shipped in #111 and is documented nowhere #131

New issue

Closed

opened 2026-07-30 23:50:47 +00:00 by kimi-bot-andresmgsl · 1 comment

kimi-bot-andresmgsl commented

2026-07-30 23:50:47 +00:00

Member

Context

The README's Install quick start shows only the GitHub channel. RIG_HOST shipped in #111 / !114 — the install channel is forge-agnostic (install.sh:40: "The forge this REPO lives on is RIG_HOST (#111), default https://github.com") — but the README never mentions the variable, so a reader on the Forgejo mirror has no documented way to install from the forge they are reading.

Surfaced by @andres in !130 (comment 4069): he wants the correct Forgejo install command visible in the README ahead of the 0.3.2 release.

Measured today (anonymous, no token):

https://forgejo.heavyduty.builders/heavy-duty/rig/raw/branch/main/install.sh  → 200
https://raw.githubusercontent.com/heavy-duty/rig/main/install.sh              → 200
https://forgejo.heavyduty.builders/heavy-duty/rig/releases/latest             → 303 → tag/0.3.0

Spec

Document the Forgejo channel in README.md's Install section, in the README's existing terse voice:

the Forgejo-native commands beside the GitHub ones — both the dev tree and the latest-release channel — with RIG_HOST=https://forgejo.heavyduty.builders set, since the script's URL and the channel are chosen independently;
one sentence naming RIG_HOST and its GitHub default (#111);
a changelog.d/<this issue>.md fragment per convention.

No other README sections change; the .../install.sh placeholder block below the quick start stays as-is.

## Context The README's *Install* quick start shows only the GitHub channel. `RIG_HOST` shipped in #111 / !114 — the install channel is forge-agnostic (`install.sh:40`: "The forge this REPO lives on is RIG_HOST (#111), default https://github.com") — but the README never mentions the variable, so a reader on the Forgejo mirror has no documented way to install from the forge they are reading. Surfaced by @andres in !130 (comment 4069): he wants the correct Forgejo install command visible in the README ahead of the 0.3.2 release. Measured today (anonymous, no token): ``` https://forgejo.heavyduty.builders/heavy-duty/rig/raw/branch/main/install.sh → 200 https://raw.githubusercontent.com/heavy-duty/rig/main/install.sh → 200 https://forgejo.heavyduty.builders/heavy-duty/rig/releases/latest → 303 → tag/0.3.0 ``` ## Spec Document the Forgejo channel in `README.md`'s Install section, in the README's existing terse voice: - the Forgejo-native commands beside the GitHub ones — both the dev tree and the latest-release channel — with `RIG_HOST=https://forgejo.heavyduty.builders` set, since the script's URL and the channel are chosen independently; - one sentence naming `RIG_HOST` and its GitHub default (#111); - a `changelog.d/<this issue>.md` fragment per convention. No other README sections change; the `.../install.sh` placeholder block below the quick start stays as-is.

kimi-bot-andresmgsl referenced this issue from a pull request that will close it,

2026-07-30 23:53:22 +00:00

docs: README install quick start names the Forgejo channel (RIG_HOST) #132

kimi-bot-andresmgsl commented

2026-07-30 23:53:42 +00:00

Author

Member

Build up: !132 — the Forgejo channel is documented beside GitHub with the exact command verified end-to-end on a clean box (rig 0.3.0 installed from this instance). Panel requested. Not touching labels; the queue state is triage's door.