rename: org and repo 'website' metadata still point at gitborg.se #393
Etiketter
Inga etiketter
area/backups
area/ci
area/control-panel
area/identity
area/infra
area/observability
area/payments
area/security
area/storage
area/web
blocked
needs-info
needs-triage
ready-for-implementation
type
bug
type
chore
type
docs
type
epic
type
feature
type
task
wontfix
Ingen milstolpe
Inget projekt
Inga tilldelade
1 deltagare
Notiser
Förfallodatum
Inget förfallodatum satt.
Beroenden
Inga beroenden satta
Referens
bitborg/bitborg-infra#393
Läser in…
Hänvisa till i nytt ärende
Ingen beskrivning angiven.
Ta bort grenen "%!s()"
Borttagning av en gren är permanent. Även om den borttagna grenen kan fortsätta existera en kort tid innan den faktiskt tas bort, kan det INTE ångras i de flesta fall. Vill du fortsätta?
Noticed while reading API responses during the §5 work. Two Forgejo metadata fields still carry
the old domain, and both are publicly visible:
Worth checking the other six repos in the same pass — these two surfaced incidentally, so the list is
not known to be complete.
Why it is worth doing rather than shrugging at
The links still work (§4a-i gave every old name a path-preserving redirect), so nothing is broken.
But this is server-side metadata rather than content, which means it was missed by the repo-wide
content sweeps — it lives in the database, not in any file, so
rg gitborgwill never find it. Itrenders on the org page and each repo's sidebar, i.e. on public surfaces, which the project's own
conventions single out.
Not in scope
The
gitborg-webpackage/image path (git.bitborg.se/bitborg/gitborg-web) is a separate,deliberate pin — §3 of the rename register, where retagging has real consequences. Do not fold it in.
Doing it
Both are ordinary
PATCHfields (/api/v1/orgs/{org},/api/v1/repos/{owner}/{repo}), so this isan API change with no Ansible involvement and no apply. Nothing derives from either field.
Acceptance
websitevalues point atbitborg.sehosts.Done 2026-08-10 — applied to the live server and verified by independent re-read. Declaration side: infra #416 (no file change was needed for this issue;
websiteis pure server metadata, which is exactly why the repo-wide content sweeps never saw it).What changed
bitborghttps://www.gitborg.se/https://www.bitborg.se/bitborg-infrahttps://git.gitborg.se/https://git.bitborg.se/bitborg-webhttps://www.gitborg.se/https://www.bitborg.se/The list was incomplete, as this issue suspected
bitborg-webwas a third stale field. Worth recording why it was hard to see:fj repo viewdoes not exposewebsite, so the field is invisible from the CLI and only appears in a raw API response or the web UI.All seven repos were checked, not just the two named. The remaining five —
bitborg-docs,bitborg-reconcile-trigger, and all three private repos (bitborg-internal,bitborg-payment,bitborg-auth-reconciler) — have an emptywebsite, so nothing was hiding behind the private-repo boundary. That closes the completeness question rather than leaving it open.How
PATCH /api/v1/orgs/bitborgandPATCH /api/v1/repos/bitborg/{repo}, each field re-read afterwards and compared. Empty fields left alone; only values containinggitborgwere touched.Needed a temporary
write:organization+write:repositoryPAT, minted for this and revoked after — no standing token has write scope (ADR 0024).Out of scope and untouched, as stated: the
gitborg-webpackage/image path.