RFC: Continuous Deployment Support

[EduardoAC]

Current behaviour

• We need to create a new branch and then attempt to merge that branch to trigger the publish

These have the following deficiencies:

• GitHub Actions doesn't trigger CI when the Octokit API creates the PR
• GitHub Actions workflow_run only applies to the branch where the version is triggered and not the PR generated.
• The fact that we need to cherry-pick when to yarn install without --immutable flag

Desire behaviour

Adding a flag called continousDeployment that allows to trigger on PR merge the following steps:

• Trigger version
• Create a commit on the main with the changes
• Trigger publish

I understand this has downsides and caveats. The idea behind it follows the same philosophy as the article Continuous deployments with Changesets + GitHub actions within the action itself rather than requiring additional setup.

Before starting work on a PoC, I would like to hear your thoughts and if it will bring value.