Santiago Fraire Willemoes

I've been thinking about this and a common pattern is to use `--` which would mean "end of the options" for `cz c`, the rest could go to `git commit`...

It's becoming increasingly popular the `--`. I think it's the right approach. It's a bit of a trade-off. Instead of `git commit -s`, you'd write `cz c -- -s`. I...

@Lee-W @Yajo About this feature, I was thinking about adding a new setting to the configuration file: ```toml # .cz.toml [tool.commitizen] workspace = true # similar word used by rust...

yes, each sub-package would have it's own `.cz.toml`. This means that each would have it's own independent version. This is a sample of a monorepo with poetry: https://github.com/ya-mori/python-monorepo You can...

Indeed, the tag issue only happens if you have many `.cz.toml`, which is the one I personally would prefer. Maybe we can add a prefix (folder-name) or something like that....

Maybe it could be part of the `buildmetadata` of semver. ``` 1.0.0+fizzbuz 2.3.5+foobar2 0.1.0+p1 ``` We just need to check if python's pep-0440 has support as well Edit: it seems...

It's a possibility, but I don't think `semver` and `pep-0440` would be able to parse a tag like that. I get: ```python InvalidVersion: Invalid version: 'submodule-v1.2.3' ``` From my understanding...

> Regarding this, for my original purpose when opening this issue, we don't use tags on those repositories. I foresee some issues with the changelog generation in this situations, as...

Hey @andres-fr thanks for the feedback. Can u expand it a bit more? The [approach you linked](https://stackoverflow.com/questions/458550/standard-way-to-embed-version-into-python-package/7071358#7071358) is kind of fine, but I'm not a fan. The intention for commitizen...

No problem, I understand what you mean, I also prefer explicit interfaces, everything else in the code is mostly explicit, no moving parts. Commands and configs are not the easy...