Automating the Release Process#2
Open
DPigeon wants to merge 4 commits into
Open
Conversation
This file contains hidden or 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.
Moved to its own PR. It was originally in #1.
This PR proposes changes to automate the release process. GitHub Actions are used to create a release from the private repository to the public one.
Automation of the Release Process
Then, the pipeline does this in background:
More Info
For this to work properly, you need to
Setup the PUBLIC_REPO_TOKEN for the public repo as a secret in private repo for it to have access to push
In public checkout, change public repositories name in
.github/workflows/release.ymlto the right one e.g replaceDPigeon/smashremix-test-publicbyJSsixtyfour/smashremixIn last step of
.github/workflows/release.yml, changeownerandrepoproperly e.gDPigeontoJSsixtyfourandsmashremix-test-publictosmashremix.