From 9b28daafabaf47b1a10d22cb11ef25bb0251e0f5 Mon Sep 17 00:00:00 2001 From: Ivan Subotic <400790+subotic@users.noreply.github.com> Date: Fri, 20 Mar 2026 17:02:01 +0100 Subject: [PATCH] docs: use one Closes keyword per issue in PR template GitHub may silently skip issues when multiple are comma-separated on one line. Use separate lines to ensure all issues close on merge. Co-Authored-By: Claude Opus 4.6 (1M context) --- docs/commit-conventions.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/docs/commit-conventions.md b/docs/commit-conventions.md index 8fd88d7..7558958 100644 --- a/docs/commit-conventions.md +++ b/docs/commit-conventions.md @@ -81,6 +81,7 @@ not found in the workspace root. ``` Closes # +Closes # ## Motivation Why this work was needed. What problem it solves for users. @@ -109,6 +110,22 @@ actionable -- not just "this is hard" but "do X instead of Y". - [ ] verification steps ``` +### Closing issues + +Use one `Closes` keyword per issue, each on its own line. Do NOT +comma-separate multiple issues on one line — GitHub may silently +skip some of them. + +``` +# Good +Closes #39 +Closes #40 +Closes #41 + +# Bad — GitHub may not close all of them +Closes #39, #40, #41 +``` + ### Why this format matters The "Challenges and Decisions" section captures the debugging journey that would otherwise be lost when commits are squashed. The