Development record
When a release cut is refused for an unfixed or deleted finding and also for an issue record under open/ that differs from HEAD, the open-records refusal gets no refusal entry of its own: emit.go raises the unfixed and deleted refusals and adds the guard's verdict as a backstop only when both lists are empty, so the uncommitted-records reason survives only in the findings verdict. A front door that acts on the refusal list fixes the findings, retries, and only then meets the second refusal.
issueresolvedminoriss-2610090642371836
When a release cut is refused for an unfixed or deleted finding and also for an issue record under open/ that differs from HEAD, the open-records refusal gets no refusal entry of its own: emit.go raises the unfixed and deleted refusals and adds the guard's verdict as a backstop only when both lists are empty, so the uncommitted-records reason survives only in the findings verdict. A front door that acts on the refusal list fixes the findings, retries, and only then meets the second refusal.
Grounds
- pursued: a cut refused for unfixed, deleted and uncommitted findings at once lists three refusals, each reason once; TestEmitRaisesEveryFindingsHalfAsItsOwnRefusal and TestLaunchShipNamesAnUncommittedRecordOnceBesideAnUnfixedFinding would show it wrong by finding the uncommitted reason missing from the refusals or its path printed twice.
Frontmatter
| id | iss-2610090642371836 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2610090642371836-when-a-release-cut-is-refused-for-an.md
open on GitHub ↗ · commit history ↗