Santiago Fraire Willemoes

Hey bruno, I copied your example, seems to be working well. You see that error because of the `--debug` flag. Which gives you extra information, but it is not returning...

I think the commit_parser regex is not exposed in the customize https://github.com/commitizen-tools/commitizen/blob/095f02e6c419b60c90aa84b8cebc9e9eacc8a391/commitizen/defaults.py#L83 and it looks like the customize is using the default from the base https://github.com/commitizen-tools/commitizen/blob/095f02e6c419b60c90aa84b8cebc9e9eacc8a391/commitizen/cz/base.py#L30 Any thoguhts on this...

Makes sense, it would completly ditch the `git` dependency. Seems nice. At the moment my only proposal would be to add a `--no-git` to `cz bump`, any other ideas? **On...

Maybe we need to document `cz bump --files-only` better, which is there already, or fix it to fit this use case. But it needs to be more clear

Agreed, that'd be helpful in the init

I cloned your repo, and I think your main issue is the `tag_format`, which includes a `v` now. I changed it like this: ```diff - tag_format: v$major.$minor.$patch$prerelease + tag_format: $major.$minor.$patch$prerelease...

Great news! What we usually do is let the github action create the tag and then push back to the repo. Here's the tutorial for github actions: https://commitizen-tools.github.io/commitizen/tutorials/github_actions/

It works fine on my side. I cloned, run `cz bump` and the tag created was `v_2.5.3` with the changelog. My conf: ``` $ cz version 2.17.11 ``` on ubuntu

think that would be possible, do you think you could add some extra examples?

All the latest errors are related to the chardet I think