Playbook 07: name a pull request's own issues as 'issue <n>', and no other #458

Merged
mesh-tools merged 2 commits from playbook/pr-issue-words into main 2026-10-21 12:17:56 +00:00
2 Commits
Author SHA1 Message Date
jochen ad0a95dc0c Playbook 07: the plural 'issues <n>' is read too; 1654 was another milestone's issue
mesh/merge-gate head ad0a95dc0c1b merged into trunk ab3ac686dcdd — pass: the change touches no module of the mesh's graph
mesh/repo-check head ad0a95dc0c1b merged into trunk ab3ac686dcdd — pass: its merge-check.sh passed
mesh/delivery delivered
2026-10-21 14:06:36 +02:00
jochen c770bc1c50 Playbook 07: name a pull request's own issues as 'issue <n>', and no other
mesh-delivery reads a pull request's issues from the words 'issue <n>' 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.
2026-10-21 14:05:28 +02:00