Fix/major version zero bump map #726
Conversation
before this commit, major_version_zero would only work with conventional commits, as the value used was not exposed to other cz rules
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #726 +/- ##
==========================================
- Coverage 97.42% 97.38% -0.05%
==========================================
Files 42 42
Lines 2022 2029 +7
==========================================
+ Hits 1970 1976 +6
- Misses 52 53 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
| class ConventionalCommitsCz(BaseCommitizen): | ||
| bump_pattern = defaults.bump_pattern | ||
| bump_map = defaults.bump_map | ||
| bump_map_major_version_zero = defaults.bump_map_major_version_zero |
There was a problem hiding this comment.
If this is not actually a default for every cz, should we move it out of defaults? I've been thinking for moving these kind of stuff from defaults for a long time but not yet have a chance to do so 🤦♂️
There was a problem hiding this comment.
Agreed, many (not all) of those "defaults" are actually part of the conventional commit cz and we are probably creating confusion by having them there
Description
It's currently not possible to modify major version zero, meaning that it only works with conventional commits.
If you have a custom rule, and you set
major_version_zeroto true, it won't find any commits, because it will be actually using the one indefaults.bump_major_version_zerowhich matches with conventional commit conventionsChecklist
./scripts/formatand./scripts/testlocally to ensure this change passes linter check and testExpected behavior
Users should be able to express the behavior when major_version_zero is true, and they have a different set of rules.