docs: point stale gitborg links at the canonical bitborg host #405

Sammanfogat

supernaut sammanfogade 1 incheckning från docs/stale-gitborg-links in i main

2026-08-09 20:31:18 +00:00

supernaut kommenterad

2026-08-09 20:20:00 +00:00

Ägare

Documentation links only. Scoped deliberately narrow — see what is excluded and why.

Changed

https://git.gitborg.se → https://git.bitborg.se in clickable links across CONTRIBUTING.md, README.md, docs/roadmap.md and docs/design/forgejo-actions-runners.md. The https:// prefix was used as the anchor precisely so bare registry paths could not be caught.

Also fixed a pre-existing broken link found while verifying: the Roadmap board was linked as /org/bitborg/-/projects, which 404s. The working form is /bitborg/-/projects. That was wrong before this PR too, in both CONTRIBUTING.md and docs/roadmap.md. docs/roadmap.md additionally still named the old gitborg org in that URL.

Every link in these four files was then fetched — all nine return 200.

Deliberately NOT changed

The old hostnames are permanent infrastructure, not stale strings. bitborg-web/scripts/check-content-style.test.mjs asserts this in a test, with the reasoning: "The gitborg.se hostnames are PERMANENT infrastructure (ADR 0039 §4: they serve the redirects indefinitely), so the hostname exemption must keep covering the OLD brand too — runbook §10 is explicit that the linters must not tighten to bitborg only." Confirmed live: https://git.gitborg.se/bitborg/bitborg-docs returns 301, not a failure.

So the following are left exactly as they are:

group_vars/all/vars.yml:145 — { host: "git.gitborg.se", to: "https://{{ bitborg_domain }}" } is the live redirect rule that makes the old hostname work. Rewriting it would either self-redirect or drop the redirect.
vars.yml:58–76 — the post-mortem of the 2026-08-05 §4b move, which quotes the observed failure (7× git.gitborg.se /v2/ 301 then 7× git.bitborg.se /v2/ 401). Replacing the old name destroys the record and makes the comment self-contradictory. Same for the rate-limit incident data in roles/caddy/defaults/main.yml and the fixed-bug note in roles/kanidm/defaults/main.yml:504.
docs/runbook.md (37 hits) — mixes operational commands that are now wrong with switchover-procedure prose where the old name is the subject. Needs a per-line pass, not a replace. Left for a follow-up.
All 34 LEGACY-PIN markers, image path segments (git.bitborg.se/bitborg/gitborg-web), the gitborg_ metric prefix, [bg]itborg dual-brand matchers, database/volume/unix-user names, and ADR 0039 itself — these belong to tranches §3/§5/§7/§8 of the rename completion plan, and several are on that plan's explicit "Do not" list.
docs/design/forgejo-actions-runners.md:43 — a recorded network measurement in prose, not a link.
docs/design/authorized-integrations-jwt-eval.md:97 — a "verified live" measurement of the OIDC discovery endpoints, tied to when it was taken. Line 7 (a doc link) was updated; line 97 was not.

markdownlint and prettier clean.

Documentation links only. Scoped deliberately narrow — see what is excluded and why. ## Changed `https://git.gitborg.se` → `https://git.bitborg.se` in clickable links across `CONTRIBUTING.md`, `README.md`, `docs/roadmap.md` and `docs/design/forgejo-actions-runners.md`. The `https://` prefix was used as the anchor precisely so bare registry paths could not be caught. Also fixed a **pre-existing broken link** found while verifying: the Roadmap board was linked as `/org/bitborg/-/projects`, which 404s. The working form is `/bitborg/-/projects`. That was wrong before this PR too, in both `CONTRIBUTING.md` and `docs/roadmap.md`. `docs/roadmap.md` additionally still named the old `gitborg` org in that URL. Every link in these four files was then fetched — all nine return **200**. ## Deliberately NOT changed The old hostnames are permanent infrastructure, not stale strings. `bitborg-web/scripts/check-content-style.test.mjs` asserts this in a test, with the reasoning: *"The gitborg.se hostnames are PERMANENT infrastructure (ADR 0039 §4: they serve the redirects indefinitely), so the hostname exemption must keep covering the OLD brand too — runbook §10 is explicit that the linters must not tighten to `bitborg` only."* Confirmed live: `https://git.gitborg.se/bitborg/bitborg-docs` returns 301, not a failure. So the following are left exactly as they are: - **`group_vars/all/vars.yml:145`** — `{ host: "git.gitborg.se", to: "https://{{ bitborg_domain }}" }` is the **live redirect rule** that makes the old hostname work. Rewriting it would either self-redirect or drop the redirect. - **`vars.yml:58–76`** — the post-mortem of the 2026-08-05 §4b move, which quotes the observed failure (`7× git.gitborg.se /v2/ 301` then `7× git.bitborg.se /v2/ 401`). Replacing the old name destroys the record and makes the comment self-contradictory. Same for the rate-limit incident data in `roles/caddy/defaults/main.yml` and the fixed-bug note in `roles/kanidm/defaults/main.yml:504`. - **`docs/runbook.md`** (37 hits) — mixes operational commands that are now wrong with switchover-procedure prose where the old name *is* the subject. Needs a per-line pass, not a replace. Left for a follow-up. - **All 34 `LEGACY-PIN` markers**, image path segments (`git.bitborg.se/bitborg/gitborg-web`), the `gitborg_` metric prefix, `[bg]itborg` dual-brand matchers, database/volume/unix-user names, and ADR 0039 itself — these belong to tranches §3/§5/§7/§8 of the rename completion plan, and several are on that plan's explicit "Do not" list. - **`docs/design/forgejo-actions-runners.md:43`** — a recorded network measurement in prose, not a link. - **`docs/design/authorized-integrations-jwt-eval.md:97`** — a "verified live" measurement of the OIDC discovery endpoints, tied to when it was taken. Line 7 (a doc link) was updated; line 97 was not. `markdownlint` and prettier clean.

supernaut lade till 1 incheckning

2026-08-09 20:20:00 +00:00

docs: point stale gitborg links at the canonical bitborg host

ci / ci (pull_request) Successful in 17s

Detaljer

2df0304ed3