GitHub introduced rulesets last year, a new way to protect branches.
More recently, rulesets now permit to add a Deploy key to the bypass list (doc).
This permits to store the private SSH key of the Deploy key in a secret, and checkout the repository using this key.
After that, the Action can now push on protected branches.
Changes
Make the Action checkout the repo using the DEPLOY_KEY secret.
GitHub introduced rulesets last year, a new way to protect branches.
More recently, rulesets now permit to add a
Deploy keyto the bypass list (doc).This permits to store the private SSH key of the Deploy key in a secret, and checkout the repository using this key. After that, the Action can now push on protected branches.
Changes
DEPLOY_KEYsecret.I've already done the following on the repo:
DEPLOY_KEYsecretDeploy keysadded to the bypass list. You can view them here.Test
At next release. I've also tested it on a test repo: https://github.com/sbellone/release-workflow-example
SFCC-384