erik/acdream
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2

docs: origin is a lagging mirror, not a stale local ref — correct the correction

Browse source 
The previous fix said the local origin/main ref had not been written
since April and was three months stale. It was not stale: a fresh
git fetch origin returned it unchanged at f6275f45, so the REMOTE was
genuinely 412 commits behind and the ref was accurate all along.

The original error was therefore never a caching artefact — it was
reading a lagging mirror as if it were the live remote and concluding
the campaign was unpushed. Recorded that way so the rule is usable:
origin here is a mirror and may lag arbitrarily; measure against
github/main or git branch --contains.

Both remotes are now at parity, 0ce54a5c.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Erik 2026-08-06 22:41:17 +02:00
parent 0ce54a5c4a
commit 677f9a1628
1 changed files with 18 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

25
docs/research/2026-08-06-c5c-closeout-handoff.md
View file

@ -15,13 +15,24 @@ alarm a successor.** The campaign was merged to `main` and pushed the same day:
7b3e2895` lists `main`.
**The measurement error, because it will recur.** This repo has TWO remotes.
`github` (`git@github.com:eriknihlen/acdream.git`) is the live one. `origin`
(`https://git.snakedesert.se/erik/acdream.git`) is a second remote whose cached
ref `origin/main` still points at `f6275f45` and whose ref file has not been
written since **April 27** — three months stale. `main` is 412 commits ahead of
that ref, which is where "388+ unpushed" came from. **Never measure push state
against `origin/*` in this repo without checking the ref's age first**; compare
against `github/main`, or check `git branch --contains <sha>`.
`github` (`git@github.com:eriknihlen/acdream.git`) is the primary. `origin`
(`https://git.snakedesert.se/erik/acdream.git`) is a second self-hosted mirror
that had simply not been pushed to since `f6275f45` — `main` was 412 commits
ahead of it, which is where "388+ unpushed" came from.
**A first correction to this correction, since it was itself stated wrongly
once:** the local `origin/main` ref was NOT stale. A fresh `git fetch origin`
returned it unchanged at `f6275f45`, so the *remote* was genuinely behind; the
ref was accurate all along. The error was never a caching artefact — it was
reading a lagging MIRROR as if it were the live remote and concluding the work
was unpushed.
**The rule:** in this repo, `origin` is a mirror and may lag arbitrarily.
Measure push state against `github/main`, or better, against the question you
actually mean — `git branch --contains <sha>`.
**Both remotes were brought to parity 2026-08-06** by the #333/#334 merge:
`main`, `github/main` and `origin/main` are all `0ce54a5c`.
---