gate: the source of a watched branch follows every merge, forward only (A-464..A-464d) #697

Merged
mesh-tools merged 3 commits from fix/47-G-untaken-merge into main 2026-11-17 01:13:08 +00:00
Member

Design 47 G, the lead's answers A-464, A-464b, A-464c and A-464d (hq 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md).

  • A-464: the gate consumes the forge bridge's merged and moves the repository's head in the source of that branch, says source-moved; at its start it compares each head with the forge's branch head (seat git) and moves every one behind; tool gate_source_follow {branch, repository, why} (hand act).
  • A-464b: a merge whose merged names no delivery group is logged as not made by a delivery group of the gate; its source-moved names no group.
  • A-464c, A-464d: every move is forward only (seat git contains), and nothing is written when the head stays.

Group with mesh-delivery fix/47-G-untaken-merge (the indexer, A-463, A-463a, A-464a); neither names the other's version.

Tests: go vet, go vet -tags integration, go test ./... pass (with the gate's tagged tests); each new test fails without its fix. Validator: the gate's manifest accepted, change and trunk (in process, 169/169). manifest_test.go now allows this one forge consume (A-464 overrides it).

Quick vs thorough: thorough (the gate follows every merge whoever made it); quick would be moving the stale heads by hand, which no tool can do and which would recur at the next direct merge.

Reviewed-by: mesh-code-reviewer for lead-47@shanks at 46f3dc8cd7 (round 2)

Design 47 G, the lead's answers A-464, A-464b, A-464c and A-464d (hq 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md). - A-464: the gate consumes the forge bridge's merged and moves the repository's head in the source of that branch, says source-moved; at its start it compares each head with the forge's branch head (seat git) and moves every one behind; tool gate_source_follow {branch, repository, why} (hand act). - A-464b: a merge whose merged names no delivery group is logged as not made by a delivery group of the gate; its source-moved names no group. - A-464c, A-464d: every move is forward only (seat git contains), and nothing is written when the head stays. Group with mesh-delivery fix/47-G-untaken-merge (the indexer, A-463, A-463a, A-464a); neither names the other's version. Tests: go vet, go vet -tags integration, go test ./... pass (with the gate's tagged tests); each new test fails without its fix. Validator: the gate's manifest accepted, change and trunk (in process, 169/169). manifest_test.go now allows this one forge consume (A-464 overrides it). Quick vs thorough: thorough (the gate follows every merge whoever made it); quick would be moving the stale heads by hand, which no tool can do and which would recur at the next direct merge. Reviewed-by: mesh-code-reviewer for lead-47@shanks at 46f3dc8cd7b37407118e22ecbeec98285f5d91fe (round 2)
mesh-tools added 3 commits 2026-11-17 01:13:02 +00:00
The forge bridge's merged moves the repository's head and says source-moved; at its start each head is compared with the forge's branch head; gate_source_follow does it for one repository by hand.

Builds: design 47 G-22 A-464, A-464b
Builds: design 47 G-22 A-464c, A-464
Also corrects the manifest test's comment, which said the gate does not hear merged (A-464).

Builds: design 47 G-22 A-464d, A-464
mesh-tools merged commit 9ade421e12 into main 2026-11-17 01:13:08 +00:00
mesh-tools deleted branch fix/47-G-untaken-merge 2026-11-17 01:13:08 +00:00
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#697