`localrepo.CloneBundle()` fails to remove origin remote
When a Git repository is cloned from a bundle, the repository config automatically sets up the origin remote. This remote is subsequently removed as it is not necessary. Reports indicate that the remote removal is sometimes failing due to origin not being defined in the newly cloned repository.
To workaround this problem, we can ignore exit code 2 errors coming from git-remote(1)
which indicate the remote does not exist.
Related: https://gitlab.com/gitlab-com/geo-customers/-/issues/204
Edited by Justin Tobler