Backport without requiring push permission.

[Carreau]

I want to upgrade Mr. Meeseeks to not require push-permissions to repositories for many reason:

1. Security
2. not clutter repos with branches named backport-pr-XXX-to-YYYY.

Thus I've created a meeseeksmachine GitHub Machine account it's like a personal account but have no human activity. With the creds of this account, I can fork, and make cross-organisation PRs, which Mr Meeseks couldn't do before due to GitHub limitation..

Using the new safe_backport, Mr Meeseeks can now backport without touching the target repository. The backport PR is created by, and come from the @meeseeksmachine account, like in this PR, @meeseeksdev is still responsible for the rest.

if you want to try it now

Change backport to safe_backport and report any potential bugs.

In the future I'll switch the backport to use the new mechanism, and remove the requirement for push permission.

[Carreau]

One of the other advantage is that pushing on same-repo was also putting pressure on CI, as both push and PR would trigger it.

[Carreau]

I've switched the default. You can use legacy_backport if there are issues.

[QuLogic]

It seems like this still creates the branch on the original repo even though the PR is opened from the @meeseeksmachine account?

[Carreau]

Hum it appears you are right. I just completely removed the old backport code (including removeing legacy_backport, and pushed a fix. The bot has been restarted so this should not hapend anymore.