I found that fetch_sha_from_remote always tries to pull from origin, and in case of pinned merges in another repo that fails because the branch is not found.
This workaround mutes the error because afterwards, git pull http://some_url some_sha23897abc will mostly succeed anyway, so there is no need to stop the flow.
I found that
fetch_sha_from_remote
always tries to pull from origin, and in case of pinned merges in another repo that fails because the branch is not found.This workaround mutes the error because afterwards,
git pull http://some_url some_sha23897abc
will mostly succeed anyway, so there is no need to stop the flow.Should address #94 as well.