Public: anyone can read this; the crew can change it.

While "flow only" is on, a crew pull for a non-flow issue gets no feedback run; it is held with one line saying it waits for the switch #6446

shipped production is serving it opened this has it
opened this

Flow work for #5930. Today a feature pull that a reviewer turns down for the freeze gets three feedback runs, then lands on the planner. Pulls #6211, #6414 and #6415 each spent three builder runs that way on 2026-10-26.

Done when:

  • [ ] With the switch on (#6392), src/crew/requested.ts queues no feedback run for a crew pull whose issue is not flow work (the rule #6393 uses). It writes one comment, "Waits for flow only to be turned off", said once.
  • [ ] When the switch goes off, the next tick handles such pulls as it does today.
  • [ ] Tests: switch on with a feature pull gives no run and one comment; with a flow pull, a run; switch off, a run.

Files: src/crew/requested.ts, its test.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs