Allow pushing to another branch / manually pushing

[thislooksfun]

Due to the way GitHub Actions work, it's currently impossible to use this plugin on a branch that has required status checks. Hopefully this will change, but in the meantime it would be useful if we could control the pushing more granularly.

Specifically what I would like to do to work around the GHA limitations is to:

1. cut the new release
2. push the resulting commit to a new branch
3. open a PR
4. use mergify to auto-merge it back in.

The problem is that I can't easily do step 2, because this package has no configuration (at least none that I could find) to control the pushing of the commit. It would be useful if there was a setting to either control which branch gets pushed to, or, even better, just a setting to say "don't push". That way the commit could be made automatically, but then we have to deal with it manually afterwards, which allows for much finer control.

[EdieLemoine]

I'm running into the same issue and can't figure out a way around it. All my repositories' workflows that use status checks are crashing because of this since my org has migrated to using GitHub Apps.

I did write actions to fake the branch protection checks on a commit, but that only works after a commit is pushed to GitHub. Which is not possible with semantic-release right now, as it will be trying to push on the branch the protections are on, so I've reached a dead end.

Currently the only "solution" is to disable all branch protection status checks, but that's obviously not something I want to do.

[iamogbz]

Related to this issue #344, which has not gotten any interaction either. Searched their plugins page and could not find a good replacement, might have to roll with a custom one.