commitizen icon indicating copy to clipboard operation
commitizen copied to clipboard

Create committing rules for projects :rocket: auto bump versions :arrow_up: and auto changelog generation :open_file_folder:

Results 316 commitizen issues
Sort by recently updated
recently updated
newest added

### Description When a dep is specified using the `{}` syntax, eg ```toml smart-open = {version = ">=5.2.0,=5.2.0,=5.2.0,=5.2.0,

good first issue
documentation
waiting-for-implementation

### Description I attempted to use Commitizen to automatically increment a version number in [`.pre-commit-config.yaml`](https://pre-commit.com/#2-add-a-pre-commit-configuration). `pyproject.toml`: ```toml ... [tool.commitizen] version = "0.0.0" version_files = [ ".pre-commit-config.yaml:Commitizen", "pyproject.toml:version" ] ... ```...

bug

### Description cz bump results in the below error $ cz bump Traceback (most recent call last): File "/usr/local/bin/cz", line 11, in sys.exit(main()) File "/usr/local/lib64/python3.6/site-packages/commitizen/cli.py", line 323, in main args.func(conf,...

bug

## Description Respect git flag `--allow-empty` when using the cli tool. ## Possible Solution Allow empty commits using the cli tool. ## Related Issue Related to #49

type: feature
issue-status: pr-created

Local versions do not have to consist of pure numbers - according to either [Semantic Version Specification](https://semver.org/) or [PEP 440](https://www.python.org/dev/peps/pep-0440/). It is common to use things like branch names or...

feature

The [docs](https://commitizen-tools.github.io/commitizen/bump/#about) state that the version can be manually bumped but I believe this is incorrect as there's no other mention of this in the docs or in the CLI...

feature

Commitizen only implements the normalized [PEP-440](https://www.python.org/dev/peps/pep-0440/#pre-release-separators) prerelease format, excluding separators between : - the release segment and the pre-release segment - the pre-release signifier and the numeral Therefore, when using...

feature
3.0.0

### Description As discussed on [on issue 287](https://github.com/commitizen-tools/commitizen/issues/287#issuecomment-717540868), we could try [Python Entry Points Explained](https://amir.rachum.com/blog/2017/07/28/python-entry-points/) or [poetry - plugins](https://python-poetry.org/docs/pyproject/#plugins) to implement a new plugin system so that package with `cz_`...

feature
3.0.0
waiting-for-implementation

### Description I have pre-commit hooks to enforce LF line endings, this fails on every commitizen commit as it writes CRLF on windows. An option to configure this would be...

good first issue
feature

## Description A breaking change was introduced in commit [5f273ce23a331eaf11623207ec4aba8b856c14f0](https://gitlab.com/nofusscomputing/projects/gitlab-ci/-/commit/5f273ce23a331eaf11623207ec4aba8b856c14f0). Current version was `0.3.0rc1` on the next version increment the version only incremented to `0.3.0` when it should have incremented...

type: bug
issue-status: wait-for-response