Read an update before you take it
A fork that is behind its parent lists the commits an update would bring, newest first, with who wrote each and how long ago. You read them, then take.
Where
- Page: the following card on a fork's home lists up to 50 commits above Take updates; a longer list ends with "and N more".
- Terminal: the Forks screen (
ton a fork behind its parent) shows the first eight commits in its confirm, and counts the rest. - API:
POST /api/v1/repos/:owner/:name/following/take?tip=<commit id>. - MCP:
take_updateswith{ "repo": "owner/name", "tip": "<commit id>" }.
The tip you saw is the tip taken
The page and the terminal hand back the parent tip the list led to. If the parent has moved since, nothing is taken and the next look shows the new list. The API answers 409 with upstream_moved and the new tip; MCP answers the same error name. A malformed tip is 422 (invalid_tip). Without tip, a take applies whatever the parent is now, as before.
A fast-forward applies that same id: the fetch that stages the parent's tip is checked against it before the fork's branch moves.
Not covered
A repository that follows an address instead of a parent here lists nothing, and its take is not tied to a tip.