pub fn unanchored_base(branches: &[String]) -> Result<Option<String>>Expand description
The base branches sits on, when that is a branch rather than the trunk:
the parentless root of a line rooted off-trunk, with layers stacked on it.
It is not part of the stack - nothing submits, pushes, merges, or
re-parents it - so callers hold it out of whatever they are about to do.
A single unstacked branch is not a base: nothing is stacked on it, and it
is usually a branch whose metadata is simply missing. That returns None,
so callers treat it as an ordinary branch (an error to submit, something
sync may still adopt) rather than silently skipping it.