Playbook 07: the plural 'issues <n>' is read too; 1654 was another milestone's issue

2026-10-21 14:06:36 +02:00
parent c770bc1c50
commit ad0a95dc0c
1 changed files with 5 additions and 4 deletions
@@ -235,10 +235,11 @@ never into the running one, unless it blocks the running one.
   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 <n>`, 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 <n>` in its description, so write `issue 1608, issue 1646`, and name a
-   follow-up or another milestone's issue in words, not by `issue <n>`.
+   issues bare, `Issues: 1608, 1646, …`, and named a milestone-2 issue as `issue 1654` and a follow-up as
+   `issues 1665, 1666, 1667`, so mesh-delivery carried 1654 and 1665 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 <n>` and `issues <n>` in its
+   description (the plural yields its first number only), so write `issue 1608, issue 1646`, and name any other
+   issue in words, never by `issue <n>` or `issues <n>`.
   **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