✨ Add fork workflow functionality

[xanjohns]

Adds the option of a "fork and pull request" workflow.

Can be enabled by specifying which user/bot account contains the forks, using the FORK input, defaulted to false.

• Changes to the cloned repository are pushed to the fork, instead of back upstream
• Pull requests' head is changed to the new branch on the forked repository

The advantage of this style is no write access is required to upstream repositories. This also means, however, that adding labels/assignees is not possible, so that has to be disabled if FORK is specified.

Note: This setup assumes the forks have already been created.

[xanjohns]

After having though about it a little more, I think it would make the most sense to include the step of actually forking repositories in this action as well, since we have already parsed the file containing the list of external repositories we are working with. I've added another commit to include the few lines needed to fork.

[BetaHuhn]

After having though about it a little more, I think it would make the most sense to include the step of actually forking repositories in this action as well

Yeah, makes sense.

Still marked as a draft, is it ready to review?

[xanjohns]

Apologies for the slow response, but yes!

[BetaHuhn]

Other than the small change, everything looks good to me.

Could you add the FORK input to the end of the Action Inputs table and add an example on how to use it to the examples section in the README?

Will merge it after that.

[xanjohns]

I've added FORK to the Action Inputs table and provided an example/description.

[BetaHuhn]

Thanks!

[BetaHuhnBot]

🎉 This PR is included in version 1.16.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀