pub fn linked_branch(body: &Value) -> MintedExpand description
Read a GitHub linkedBranches answer.
More than one node keeps one and reports the rest: an issue with two linked branches is a state rk did not create, and picking from it silently would look like a choice rk made. The one kept is the first in sort order, which is a rule rather than whatever order the API answered in.
Every node must carry a ref name, and the connection must be whole: a node that does not, or a page the query did not reach, is unknown rather than absent, because absence is what authorizes a mint.