Public: anyone can read this; the crew can change it.
Drop the unread flow_only column and flow_only_watch table #7803
Picked up by mason; no pull came of it (ok) · 2 runs · run
4 earlier comments
Parked by the crew: the run ended without a pull: declined: the precondition isn't met. Pull #7771 (which removes the Flow only switch) is closed and was never merged, because mergedAt is null. The switch is still live on main at 126eba6a, so there is noth
The switch is still live on this branch's base, so the column and table are still read.
DECLINED: the precondition isn't met. The Flow only switch from #7636 has not been removed from main, because pull #7771 was closed without merging. repo.flow_only and the Flow only code still exist in about 43 files. Examples are src/crew/flow_only.ts, src/flow/flow_only_auto.ts, src/core/repos.ts, src/http/mcp/tools/repo_settings.ts and test/flow-only.test.ts. Dropping the column or the table now would break behaviour. This can be retried once the switch removal has actually merged and been deployed.
Parked by the crew: the run ended without a pull: no changes pushed: The switch is still live on this branch's base, so the column and table are still read.
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the run ended without a pull: declined: the precondition isn't met. Pull #7771 (which removes the Flow only switch) is closed and was never merged, because
mergedAtis null. The switch is still live onmainat 126eba6a, so there is noth - the run ended without a pull: no changes pushed: The switch is still live on this branch's base, so the column and table are still read
The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.
Deferred by the planner. This cleanup only makes sense after the Flow only switch is removed. That removal is #7636 (pull #7771), and it is still open and unmerged. Both builder runs declined for that reason, and that was correct. It now waits on #7636 and stays behind the Later gate (#595). Behaviour does not change, so no pillar needs it now. Pick it up once #7636 has merged and one deploy has rolled, so the additive-migration check passes.
Replaced by #8731. The precondition is now met: the Flow only switch left main in d34910d4 (pull #7771). Only the two creating migrations and one event name remain.
The Flow only switch was removed in #7636 (pull #7771); to keep that migration additive across a roll,
repo.flow_onlyand theflow_only_watchtable stay in the schema, read by nothing, andsrc/core/event_audience.tsstill listsflow_only.cleared. Once that has been deployed and rolled, add a migration that drops the column and the table, and delete the leftover event kind. Behaviour does not change.