Streamline gem release with bundler gem task release override #41
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.
Override default gem
release
task with our own to customize behavior to make releasing as simple and straightforward as possible.We don't want the
release:rubygem_push
task to execute at all, even accidentally, since #31 publishes the gem automatically with GitHub as a trusted publisher. (Previously we usedgem_push=no bundle exec rake release
to release without the gem push, but that's easy to forget).Since we're overriding
release
, we also use it to automate creating a GitHub release. No more having to manually run the command and edit release notes, etc.