Hey @sindresorhus, i really like this package and our team is using it in almost every npm related project.

tl;dr

Introduce a --remote option to configure the remote-repository to push the code to.

Description

One thing we have to "tweak" everywhere is to manually push the code to the upstream, which is caused by personal preferences of settings the default remote.

I prefer to use my remote-repository (mostly called origin) as the default branch and not the projects remote-repository (upstream).

So when i do np --no-yarn the tag is pushed to the upstream but the code changes are pushed to the default branch (origin).

So our current npm script looks like:

"release": "np --no-yarn && git push https://github.com/organization/project.git master"

The idea of the --remote option would be to end up with a call like this:

"release": "np --no-yarn --remote=upstream"

Possible implementation

The implementation should be straight forward by passing the option to the git-util lines
https://github.com/sindresorhus/np/blob/main/source/git-util.js#L221 and
https://github.com/sindresorhus/np/blob/main/source/git-util.js#L230.

Alternatives

Alternative No.1:
It's actually not a big thing but a nice-to-have config option.
So the alernative would be to keep the manual push behind the np stuff.

Alternative No.2:
Push the code to the repository configured in the package.json via repository, instead of pushing it to the default remote.