{{ message }}
feat: draft of the --empty parameter - #696
Closed
12rambau wants to merge 28 commits into
Closed
Conversation
Fixes commitizen-tools#607 BREAKING CHANGE: Python 3.6 is not officially supported anymore. Please migrate from 3.6 to 3.7 or greater.
…ytest-freezer` removing warnings
…n loading Plugins are now loaded using the `commitizen.plugin` entrypoint while legacy plugin are not loaded anymore but a warning is raised when one is seen. Fixes commitizen-tools#495 BREAKING CHANGE: Plugins are now exposed as `commitizen.plugin` entrypoints
… versions providers
Reads version from the repository last tag matching `tag_format` Fixes commitizen-tools#641
Topological ordering should be used when ordering commits in changelog history. This allows commits to be shown properly in the order they were added to the codebase, even if non-linear merges were used
…mmit-order fix(commands/changelog): use topological order for commit ordering
Running tests concurrently can cause temporary files, such as the file used to backup the commit message, to be deleted by one test but accessed by another test later on.
…lease feat(changelog): add merge-prerelease flag
…-tools#686) * feat(bump): version_provider=semver optional option to make version compatible with semver Signed-off-by: apkawa <apkawa@gmail.com> * refactor(bump): version_provider rename to version_type; `pep` option rename to `pep440` Signed-off-by: apkawa <apkawa@gmail.com> * docs(bump): add `version_type` info to config.md Signed-off-by: apkawa <apkawa@gmail.com> * refactor(bump): to use VersionProtocol interface instead packaging.Version subclass Signed-off-by: apkawa <apkawa@gmail.com> * test(bump): `VersionProtocol` workaround mypy for py==3.7 Signed-off-by: apkawa <apkawa@gmail.com> * fix(changelog): `changelog` command does not find version tag with `version_type=semver` option Signed-off-by: apkawa <apkawa@gmail.com> * refactor: minor review fixes * test(changelog): fix test_changelog_incremental_with_merge_prerelease issue with freeze_time Signed-off-by: apkawa <apkawa@gmail.com> --------- Signed-off-by: apkawa <apkawa@gmail.com>
Contributor
Author
|
any specific reason why this PR was removed ? is the |
Member
|
I apologize, I don't know why it was closed (and it doesn't let me open it again). Please feel free to open a new one |
Contributor
Author
|
Let me base it directly on v3 it will everyone's life easier |
Member
4 tasks
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.

Description
First draft of a new feature. The idea is to grant the user the capability to run
cz bumpwithout prior commits. The reasons are described in the associated issue.here we add an
--emptyparameter to the bump methodwhen this parameter is set and if no increment is find, a automatic "PATCH" is released.
I'll wait for your feedback before working on tests and documentation.
Checklist
./scripts/formatand./scripts/testlocally to ensure this change passes linter check and testAdditional context
Fix #662