From e8a2134d949606ca9843ef4e87e4875527244860 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 06:12:02 +0100 Subject: [PATCH] =?UTF-8?q?Answer=20A-227:=20merged=20gains=20base,=20as?= =?UTF-8?q?=20=C2=A7714=20says;=20A-221=20and=20A-223=20withdrawn?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index d3a4147c..573627cf 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -186,3 +186,6 @@ the principle that settles it, cited as "design 47 G A-n". `mesh-compose` once per node-engine fingerprint among the machines (the change's build where the change alters the node-engine, §63), the program read from that fingerprint's catalog entry through `entry`, each run's request joining the inputs of the machines on that fingerprint. +- **A-227** (withdraws A-221 and A-223; §714, §715) As design line §714 says, a merged message gains `base`, the + watched branch it landed on; `branch` stays the pull request's branch and `head` its head commit, as today; + `pushed` keeps `branch` for the branch pushed and gains `before`.