docs: repoint commit references after the history rewrite

The anonymisation rewrite of 2026-08-07 gave every touched commit a new SHA, leaving the references in these documents pointing at objects that no longer exist. The mapping was reconstructed from the backup branches and each pair verified by tree and commit message before substituting.

Prefix lookups were built for lengths 7 to 12 and any ambiguous prefix would have been skipped; none were ambiguous across all 251 pairs.
This commit is contained in:
Thore Cimbal
2026-08-09 12:00:00 +00:00
parent f0174decc1
commit c341faf521
+1 -1
View File
@@ -84,7 +84,7 @@ If the job fails (merge conflict, or the SOPS check finds an unencrypted secret
it fails **loudly and changes nothing** — the pipeline stays red until someone looks.
That red pipeline is the alarm; there is no separate reminder. Manual fallback, should
it ever be needed: fetch the branch, merge into main locally, push to git.lab (worked
example: 2026-08-01, commit `640c934`). If the mirror lags, force it via the GitLab API
example: 2026-08-01, commit `717638d`). If the mirror lags, force it via the GitLab API
`POST /projects/<id>/remote_mirrors/<mirror_id>/sync`.
## Repository Structure