From 3f0f6483c844f31fd9d7c4bc17ca3902fb8efa56 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 06:10:34 +0100 Subject: [PATCH] Answer A-223: the pull request's own branch is head-branch Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 2 ++ 1 file changed, 2 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 a0fa67bf..385335f4 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 @@ -171,3 +171,5 @@ the principle that settles it, cited as "design 47 G A-n". the bus, not acknowledged; at its start the runner reads, for each run pipeline with no steps yet, its candidate's revision through `revision`, so a placing lost while it was down is taken up. A run's rerun asks with the candidate's catalog half. An unanswered drop is said `call-unanswered` on a five-minute bound key's expiry. +- **A-223** (corrects A-221; principle 8) A merged pull request's own branch is `head-branch`; `head` stays the head + commit, as everywhere in the forge messages.