Repository with different remote silently fails

When performing a git pull against https://github.com/foo/repo, a subsequent pull against https://github.com/bar/repo does not respect the new remote.

I tested this by switching from cloning a remote repo to using a `file://` remote for the second clone. However, I suspect that this is not an artifact of file URLs, and is rather a remote-check that we're missing.