feat(github): forkOrgs, forkCreate

[rarkins]

Changes

Adds new options forkOrgs and forkCreate

Context

These features will be used by me in the Forking Renovate app a part of some necessary migrations.

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please tick one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[rarkins]

My goals are to:

• migrate the forking renovate app from using github.com/renovate-bot for all its forks and instead to an open source org (forkOrgs=[new, existing])
• use dual app tokens for both original and forked repos instead of a PAT, and therefore skip actual forking within the Renovate logic itself (forkCreate=false)

[viceice]

sounds good

[viceice]

btw: if you fork to an org, the original repo maintainer can no longer update renovate branches in the fork by default. you would need to add them with write access to the fork to get it working.

[rarkins]

btw: if you fork to an org, the original repo maintainer can no longer update renovate branches in the fork by default. you would need to add them with write access to the fork to get it working.

The challenge is:

• I need to use app tokens instead of PAT
• App token with permissions to create a PR in the parent repo wouldn't have permissions to enable "maintainers can modify" in the forked repo anyway

I'll still have a PAT on the backend (for doing the forking out of band) so maybe I could add a scheduled background process which detects maintainer in the parent repo and invites them to the forked repos. They may need to accept that invite though (which isn't necessary for maintainers can modify).

https://github.com/orgs/community/discussions/5634

[viceice]

otherwise LGTM

[viceice]

@zharinov can we detect a comment to force a test run? so we don't need to move out of draft mode?

[zharinov]

I don't think there is an easy way to do it. Seems like you either have permissions to re-run jobs, or you're not.

[viceice]

just a docs question, otherwise LGTM

[renovate-release]

🎉 This PR is included in version 35.132.0 🎉

The release is available on:

• GitHub release
• 35.132.0

Your semantic-release bot 📦🚀