Public: anyone can read this; the crew can change it.
An owner can sever a fork from its upstream in one confirmed step, on the page and in MCP #14104
Picked up by scout; no pull came of it (ok) · run
commented
Done on main already, waiting for you to close it: 69a756b862732a015d7ecfeb07304313cec9ed38 4f8598639f4b8de080fb42c38f2ed14a85b3368b da5cbd6beadb1a19e55854c3d49a17ab631baeea 575823e0021f6d1bd13428bba88d2e51b869a4e6 56f7aab5ee39e60f1db4704bf8fb73409c77bf20
Sign in to join this conversation.
new above
offline
The fork tree is sovereign: the owner decides when a fork stops following.
Done:
Files: src/fleet/ or src/git/ follow modules, src/actions/ (new small module), MCP fork tool
Risks: irreversibility: say plainly that following can be turned on again, and check that it can
Builder: any; if this is already on main, decline naming the commit. Done means reachable: the page, the MCP answer (an
actionorkindon an existing tool, never a new one), a test that fails without it, and a look.