Add autorelease workflow#25
Merged
Merged
Conversation
On push to master, extract the version from lib/ci_helper/version.rb and, unless a release for that tag already exists, build the gem, push it to RubyGems, and create a GitHub release with the gem attached.
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
1 participant
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.
Adds
.github/workflows/release.ymlto automate gem releases.On every push to
masterthe workflow:lib/ci_helper/version.rb→ tagvX.Y.Z.ci_helper.gemspec(Ruby 3.4).GEM_HOST_API_KEYsecret..gemattached and auto-generated release notes.Modeled on the helmsnap release workflow, minus the Docker image steps since this gem ships no Dockerfile.
Required setup
GEM_HOST_API_KEYrepository secret containing a RubyGems API token with push access to theci-helpergem.