Let a small fix cover two or three related issues in one repository (playbook 08)

2026-10-15 22:37:12 +02:00
parent 409fa9bbc9
commit a227f98bdd
1 changed files with 7 additions and 0 deletions
@@ -4,6 +4,13 @@
 a missing check, a wording, a playbook or design edit. Anything larger, or anything that needs a change in a
 second repository first, is a feature and follows [playbook 07](07-feature-branches.md).

+**Related issues in one fix.** A small fix may cover two or three related issues when they are in the same
+repository, mostly in the same module, and together still fit in about an hour: they touch the same files, or
+one would be wrong or unsafe without the other (switching a clipboard's history on before its history tool stops
+handing out what was copied). Each issue is named in the commit and the pull request and moved to `fixing`,
+and each is resolved on its own once the fix is delivered. More issues, a second repository, or more than an
+hour is a feature.
+
 **Who runs it.** Anyone who writes code, engineers and agents alike.

 ## The aim