A planned project finishes with its runs' known gaps dropped #270
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What happens
Each run's summary lists what it left Not done. Re-planning folded those into the next item in runs 125 and 126, then stopped doing it:
The project then reported "every item of the plan is done".
Fix
Done when
A finished project shows every gap its runs reported, and none is silently dropped.
From the #260 re-run's transcripts.
Shipped in #301 (
5355515, deployed). It's part ofplanned-projects-finish-right, archived once the change's other issues are verified.Seen on production in run 139 (the first item of cmoriarty/breakout-planned):
script.update-plancarried it intoPLAN.md's new## To check, naming the run's change (breakout-game), in the tick commit.add-game-sounds) around the sound hooks this run built, and kept the gap, which only a person can check.check-replanpassed.