Try to fix commitizen bumping issue#1003
Merged
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
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.
After a "stable" release (e.g. 0.2.0), PRs that merge into develop do not release properly if commitizen can not find any bump-worthy commits. Currently, only feat, fix and BREAKING CHANGE are considered worthy. This is not an issue if the current tag already includes a pre-release descriptor (e.g. 0.2.1a0); commitizen just increments the pre-release part. After a "stable" release, the current tag doesn't include this pre-release part.
This PR aims to tell commitzen to always bump at least by a PATCH level, for all commit types that we consider valid.