From 6cd754aeed0f2f750e4f155f5ce29014c1eac1f8 Mon Sep 17 00:00:00 2001 From: Derek Lewis Date: Sat, 15 Aug 2026 03:40:04 +0000 Subject: [PATCH] =?UTF-8?q?=F0=9F=93=96=E2=9C=A8=EF=BC=9Asay=20how=20a=20p?= =?UTF-8?q?ull=20request=20reaches=20the=20history?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The handbook described the rules a message answers to without saying what happens to it afterwards. Labelling a pull request `commit-queue` squashes it into one commit whose body keeps every message it contained. Signed-off-by: Derek Lewis Assisted-by: Claude-Code:claude-opus-5 --- collections/_docs/handbook/style/commit-messages.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/collections/_docs/handbook/style/commit-messages.md b/collections/_docs/handbook/style/commit-messages.md index 842d343d9..d6b416f37 100644 --- a/collections/_docs/handbook/style/commit-messages.md +++ b/collections/_docs/handbook/style/commit-messages.md @@ -10,6 +10,11 @@ The rules below are checked by `nps verify.commits`, which runs on every pull request. Nothing here is a matter of taste that the checker is unaware of: if it passes, the message conforms. +What lands is built from these messages rather than typed again at merge time. +Labelling a pull request `commit-queue` squashes it into one commit whose body +keeps every message it contained, with the trailers gathered where git reads +them and `PR-URL` added. + ## Subject The first line names a classification and then says what the change does: