(2c95d38) Gate a blocker by the column it is in, not by whether it is done, and bump to 0.33.1
check_blockers refused every move while a blocked by target was still open, so a dependent sat in backlog until its blocker landed even when the blocker was in reviewing and its code was there to build on. The way out was -f, which also waives the backward and skipping guard, on every move for as long as the pair existed. The rule is now the columns: a ticket may stand level with what it waits on but never ahead of it, so a blocker in reviewing lets the dependent be committed and reviewed and gates only done. util::blocks_move is the one place it is decided, taking the status moved into and the blocker's own, and mv passes the target through. A finished blocker still holds up nothing, answered through is_open, and a target of discarded is answered by name rather than by its place in Status::ALL, where it sits last. The refusal now names the status moved into and only the blockers still behind it: a dependent told to wait for work already ahead of it has nothing to act on. The board asks the same function about the column one stage ahead, so the blocked mark means the card cannot advance rather than that a dependency was ever recorded, which also takes it off cards in the two terminal columns. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5
parent
9c224fb768
commit
ead3c4340d
+6
-2
@@ -35,8 +35,12 @@ comments are where the intent moved after filing. A criterion that contradicts a
|
||||
is one of the more useful things you can find: it means the ticket was not updated when
|
||||
the plan changed, and one of the two is now lying to whoever reads the board.
|
||||
|
||||
Read the Relations too. A `blocked by` that is not done, or a `regression of`, changes
|
||||
what the change was allowed to do and what the review has to check twice.
|
||||
Read the Relations too. A `blocked by` that has not landed, or a `regression of`, changes
|
||||
what the change was allowed to do and what the review has to check twice. A ticket
|
||||
reaching review while its blocker is still in review is allowed by the board, so it is
|
||||
normal rather than a fault, and it is exactly the case where the code under review may be
|
||||
resting on work that has not landed: check that it does not assume the blocker is
|
||||
finished.
|
||||
|
||||
## 2. Find the work
|
||||
|
||||
|
||||
Reference in New Issue
Block a user