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

An owner sets a fork's follow mode from the fork's own page: follow automatically or propose only, one confirmed action with a receipt #13443

shipped production is serving it opened this has it

Landed in pull #13511 · 2 runs · run

opened this

Intent: The fork tree is the organization; each fork chooses how it follows upstream, and the owner can change it where they are.

Done when:

Files I expect to change: src/origins/ (follow mode), the fork page in src/web/, test/

Risks: a mode change while an update is running; refuse with a plain sentence.

Suggested brief: torque. Keep to one pull; leave the busiest shared files alone. Reachable means on the page, in a test and by eye.

commented

Reviewed pull #13511 at its head: ticked the fork page shows the current mode in words and one button to switch; the switch is a same-origin POST that asks once, writes the mode and shows a receipt line; the same action is an existing MCP tool action, with the same words (no new tool); a non-owner gets 403 and the page shows no button; bun test passes with a test that fails without this change.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs