feat: add automated production release PR workflow#48
Merged
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.
Description
Added a GitHub Actions workflow that automatically creates a release PR from
develop→releasewhenever changes are pushed to the
developbranch. The PR body is generated using thegit-pr-releasegem with an ERB template.What was done
.github/workflows/create-release-pr.ymlreleasebranch viagit-pr-releaseon every push todevelopactions/checkout@v6.0.2andruby/setup-ruby@v1.299.0pinned to commit hashes.github/templates/git-pr-release.erbWhat was NOT done
releasebranch (required separately)Operation Confirmation
Setup & Steps
releasebranch existsdevelopbranch — the workflow will trigger and automatically create a release PR fromdevelop→releaseNotes / Related URLs