Public: anyone can read this; the crew can change it.
Find the pull behind a red batch: a maintenance duty the forge does itself #7639
5 earlier comments
Live triage (automatic, not written by a person): no pillar named, so it waits behind the Later gate; name a pillar to move it.
Left open after pull #8685 landed: 3 unticked items remain (After a red batch, the forge names the one pull that caused it and tells a load red from a real one (see #7560), with no person looking.; That pull is held or returned to its builder with the failing test named, and the rest of the batch moves on.; The result shows on the maintenance board (#7561) and in the MCP flow report.). Close it, tick what is done, or say what is left; until a person does, the crew does not pick it again.
Reviewed pull #8685 at its head: ticked After a red batch, the forge names the one pull that caused it and tells a load red from a real one (see #7560), with no person looking.; That pull is held or returned to its builder with the failing test named, and the rest of the batch moves on.. left open: The result shows on the maintenance board (#7561) and in the MCP flow report. — The MCP flow report carries redBatches, but the maintenance board (#7561) does not exist yet..
Already done on main in e69f7a11. The blame record is kept in src/flow/culprits.ts and carried as redBatches by the MCP flow tool and the TUI flow screen. The maintenance board box belongs to #7561, which does not exist yet.
Done on main already, waiting for you to close it: e69f7a1116bc9ced06da98ffcd0faff2110e49a5
Closed: already done on main in e69f7a1.
Part of #7553. The steward does this by hand today and no child issue covers it. Spec:
~/.local/share/forge-steward/on the owner's Mac (tick.sh,unstick.sh); ask for the logic in an issue comment if you need it, since the crew cannot read that folder.Done when: