pub fn remote_only_commits(
branch: &str,
tracking: &str,
) -> Result<Vec<(String, String)>>Expand description
The commits tracking (a <remote>/<branch> ref) has that branch lacks
and that have no patch-equivalent already on branch - the commits a
force-push would silently drop, e.g. one committed straight on the host’s
web UI. (short-sha, subject) oldest-first, the order to cherry-pick them.
Empty in the normal post-rebase case, where every remote commit is
reproduced locally under a new hash.