Skip the release commit when nothing needs committing - #56
Open
bircni wants to merge 1 commit into
Open
Conversation
Empty commits were noise for tag-only releases. Keep tagging and pushing, and document versions as language-agnostic release automation.
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.
Closes #52.
If no files need to change, skip the release commit and tag
HEADinstead of creating an empty--allow-emptycommit. Tag, push, and--releasestill run. A changelog that still needs dating is committed as before, and--allstill commits tracked changes. Named files that would not change still error, so a wrong base version cannot slip through.The README now describes
versionsas language-agnostic release automation, with Node, Python, tag-only, and--releaseexamples.