Development record
When a feature's build changes files that open issues also name, those issues stay open until a separate drain lane gets to them, even though the build has the files open, reviewed and tested at that moment. The product thinker suggested on 2026-10-16 that a feature's build trigger the drain on its own files, so that every eligible issue in the code the feature touches is fixed while the feature is being built and tested.
issueopenminoriss-2610161653005769
When a feature's build changes files that open issues also name, those issues stay open until a separate drain lane gets to them, even though the build has the files open, reviewed and tested at that moment. The product thinker suggested on 2026-10-16 that a feature's build trigger the drain on its own files, so that every eligible issue in the code the feature touches is fixed while the feature is being built and tested.
Frontmatter
| id | iss-2610161653005769 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610161653005769-when-a-feature-s-build-changes-files.md
open on GitHub ↗ · commit history ↗
References1
- iss-2610161652341096A drain opens one lane per issue, even when several eligible issues touch the same files. Each lane pays its own branch, review, preflight and pull request, and the lanes then contend for the same footprint, so issues in one file are fixed one after another, each waiting on the last one's merge. The product thinker asked on 2026-10-16 that a drain bundle the issues that touch the same files and fix them in one go.blocked by