Wei Lee

This sounds to be a great solution. But I'm a bit worried about the maintenance cost and inconsistency between each format. @woile What do you think?

Sounds like an interesting feature 🤔 @woile what do you think? --- In our team, we usually merge / rebase the main / master branch back to feature branch so...

I'm not sure why the version format shown on changelog should be $version instead of "TAG_NAME$version". Is there any document indicate this? @Woile do you recall how you design it?...

Hi @Bogay , thanks for reporting the issue. I just traced the code a bit. Due the detection [here](https://github.com/commitizen-tools/commitizen/blob/master/commitizen/config/__init__.py#L41), commitizen finds no valid config file and assume such file does...

Looks more like a feature to me 🤔 as you said `cz may behave correctly.`. Thus, I'll relabel this issue as `feature`. we could discuss more if you deem otherwise...

Thanks for reporting! I think we can solve it by catching such exception in [read_cfg](https://github.com/commitizen-tools/commitizen/blob/master/commitizen/config/__init__.py)

Maybe what we need is adding it to the [FAQ page](https://commitizen-tools.github.io/commitizen/faq/) might be a good idea

Sorry for the late reply. Yep, this is something we missed. Would be great if you're interested in sending a PR 🙂

Back to the time `cz_customize` was designed, it was not designed to have any default value. But there might be some default values accidentally added to `cz_cutsomize`. What's in my...

We're out of bandwidth to implement this feature these days. PR is welcome 🙂