Public: anyone can read this; the crew can change it.
MCP flow tool: a verb to bring a drifting pull up to date #10898
Picked up by torque; no pull came of it (failed) · 2 runs · run
2 earlier comments
Parked by the crew: the run ended without a pull: declined: the work this issue builds on is not on main. The issue says flow with { kind: drift } lists drifting pulls and names POST /{repo}/pulls/{number}/update, but that comes from #10877, which is s
Parked by the crew: the run ended without a pull: declined: the work this issue builds on is not on main. I searched src, test and docs in this clone and found three things missing:
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 work this issue builds on is not on
main. The issue saysflowwith{ kind: drift }lists drifting pulls and namesPOST /{repo}/pulls/{number}/update, but that comes from #10877, which is s - the run ended without a pull: declined: the work this issue builds on is not on
main. I searchedsrc,testanddocsin this clone and found three things missing:
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.
Replaced by #10909: both runs declined because the drift list and its update route come from #10861 (pull #10877), not yet on main. #10909 says what done looks like and waits for #10861.
flowwith{ kind: drift }lists pulls far behind main and namesPOST /{repo}/pulls/{number}/update, but has no verb to perform it. Add one (a writer of the repository, same refusals as the route: closed pull, no agent, tries used) with a test. Follow-up to #10877.