From c770bc1c5023de7e858f5d7d10db556b8aa1ced2 Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 21 Oct 2026 14:05:28 +0200 Subject: [PATCH] Playbook 07: name a pull request's own issues as 'issue ', and no other mesh-delivery reads a pull request's issues from the words 'issue ' in its description; okioki #9 listed its own bare and named two follow-ups that way, and the Approve's ask named the follow-ups. --- 00-META/process/07-feature-branches.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/00-META/process/07-feature-branches.md b/00-META/process/07-feature-branches.md index 9214cffc..03c1433d 100644 --- a/00-META/process/07-feature-branches.md +++ b/00-META/process/07-feature-branches.md @@ -234,6 +234,11 @@ never into the running one, unless it blocks the running one. `Reviewed-by: at ` (the issue 1022 note gives its form). mesh-delivery reads it at every new head and puts it in the Approve's ask; a missing line, or one naming another commit, is said first in the ask. It is never a gate. + **The description names its issues as `issue `, and only its own** (2026-10-21: okioki #9 listed its four + issues bare, `Issues: 1608, 1646, …`, and named two follow-ups as `issue 1654` and `issues 1665`, so mesh-delivery + carried the two follow-ups as the pull request's issues and the Approve's ask named them): mesh-delivery takes a + pull request's issues from the words `issue ` in its description, so write `issue 1608, issue 1646`, and name a + follow-up or another milestone's issue in words, not by `issue `. **A catalogue pull request that removes a module, or a subject a module names, is also judged by the controller's unit tests against the catalogue's branch**, because those tests read the catalogue and no check of the catalogue runs them: on 2026-10-20 mesh-catalog #381 removed the old delivery module, and every