Santiago Fraire Willemoes
Santiago Fraire Willemoes
Your understanding is correct. `version` is only for the commitizen provider. Would you mind opening a new bug ticket with more information so we can take care of it. A...
Do you want `versionchanged:: 0.1.1` to be updated on every new release?
I like the idea, what do you think @noirbizarre @Lee-W ? What I don't like from the example is that once you update with the new version, this block: ```...
I think conventional commits only defines `feat` and `fix` and you can always add the `BREAKING CHANGE` block. All others should be user defined. I think our conventional_commits_cz is outdated,...
Can you share your toml configuration?
I think it relates to #688 what do you think?
Can you explain a bit more? Would `--files-only` work for you? https://commitizen-tools.github.io/commitizen/bump/#-files-only Commitizen creates a commit because it *can* update files depending on the version type used, the changelog and...
I think you could achieve something like that using the version provider `scm`, but I'm seeing some bugs on it. ``` [tool.commitizen] name = "cz_conventional_commits" tag_format = "$version" version_provider =...
@Lee-W @noirbizarre do you have any thoughts on this? how should commitizen behave under this circumstance? the circumstance: - commitizen reads the version from scm - changelog is not created...
That is (my) the expected behavior. But it's not working atm. If you update the readme or version files, it's creating the bump commit and everything works fine. If you...