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

A pull drifting far behind main is flagged on /flow with the one action that rebases it #10861

shipped production is serving it opened this has it
opened this

src/flow/alarm_drift.ts (more than 25 landings or 6 h behind main) works and nothing reaches it.

Done when:

  • [x] /flow lists drifting open pulls (number, how far behind) with the existing rebase action beside each, and the flow MCP tool answers the same list.
  • [x] The drift read is cached as the module already allows; /flow stays inside its budget (Server-Timing shows the phase).
  • [x] src/flow/alarm_drift.ts leaves scripts/unreached-allow.json; a test with a fixture repository finds the pull listed.
commented

Reviewed pull #10877 at its head: ticked /flow lists drifting open pulls (number, how far behind) with the existing rebase action beside each, and the flow MCP tool answers the same list.; The drift read is cached as the module already allows; /flow stays inside its budget (Server-Timing shows the phase).; src/flow/alarm_drift.ts leaves scripts/unreached-allow.json; a test with a fixture repository finds the pull listed..

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs