Artifact e648dbe67f01c6838299a275f4d581b43129f1095b3c4e161a425789dced0841:
- File
internal/index/landingmerge_test.go
-
2026-08-26 11:19:27
— part of check-in
[06475f5aee]
on branch landing-merge
— Link a landing to the check-in it produced
settled_by names the reply that decided the state, not the commit, so this was assumed to need an upstream change. It does not: a merge check-in lists its primary parent first and the branches it merged after, so ord > 0 is the branch tip that landed, and the landing knows which branch it proposed. Structural, not a text or time heuristic. Resolves 18 of 18 accepted landings in this store.
Bounded by when the landing OPENED, not when it was accepted: the merge lands before the artifact recording it is written.
The landing page says what it landed as; a merge row on the timeline names the proposal and who approved it. Decorated, not collapsed — a merge is a real DAG node and hiding it would leave the graph drawing edges to a row the timeline does not show. (user: dmestas, size: 5211) [annotate] [blame] [check-ins using]
- 2026-08-26 11:24:35 — part of check-in [23cec0f0fd] on branch trunk — Accepted. The link was in the DAG the whole time, and the history is finally being read. (user: dmestas, size: 5211) [annotate] [blame] [check-ins using]
-
2026-08-26 11:19:27
— part of check-in
[06475f5aee]
on branch landing-merge
— Link a landing to the check-in it produced