build: use deploy key to release #34
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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