Change default behaviour to not create release commit#16
Merged
william-lee-epigenesys merged 17 commits intoJun 12, 2026
Conversation
…tting other staged changes
…as a dirty working tree
Contributor
|
in lib/capistrano/tasks/branches.rb ensure that the error message "Cannot determine commit to deploy as BRANCH environment variable is not set and LATEST_RELEASE_TAG constant in version.rb could not be found" is adjusted to take into account the new behaviour |
ClearCarbon
approved these changes
Jun 11, 2026
9f5eed5
into
tasks/gem-cleanup
4 of 5 checks passed
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.
releasecommand by defaultconfig/version.rbby defaultEpiDeploy.create_release_commitoption, defaultfalseto revert to the previous release behaviourconfig/version.rbexists to prompt deletion--allow-dirtyflag