Having a remote named something other than 'origin' breaks `lerna publish`

Expected Behavior

In a project with a default branch named something other than 'master', and/or a default remote named something other than 'origin', I should be able to lerna publish without receiving an error.

Current Behavior

Attempting lerna publish yields the following error:

❯ excmd master ⟰  lerna publish       
lerna notice cli v3.20.2
lerna info current version 1.0.0-secondary-rollup-package.0
lerna ERR! ENOREMOTEBRANCH Branch 'master' doesn't exist in remote 'origin'.
lerna ERR! ENOREMOTEBRANCH If this is a new branch, please make sure you push it to the remote first.

Possible Solution

Providing a flag to disable the ENOREMOTEBRANCH checks, or better yet, not hardcoding any assumptions at all about branch/remote names into the tool, would be ideal. ❤️

Steps to Reproduce (for bugs)

lerna.json

{
   "packages": ["packages/*"],
   "command": {
      "bootstrap": {
         "hoist": true,
         "strict": true,
         "nohoist": ["bs-*", "ppx-*", "**/bs-*", "**/ppx-*"]
      },
      "run": {
         "stream": true
      }
   },
   "version": "1.0.0-secondary-rollup-package.0"
}

Executable	Version
lerna --version	3.20.2
npm --version	6.14.5
node --version	v12.16.0

OS	Version
NAME	VERSION
macOS Big Sur	11.1

[rbirkgit]

“–git-remote xxx” solved it for me. With it I was able to use a different remote name than origin.

[mantou132]

I have the same problem, my reason is the same name of Tag