Wei Lee

> Could the `-- ` be specified in a configuration file as a default option therebye avoiding having to add it to the command line everytime? (and on that point...

I don't get how we could use `workspace = true # similar word used by rust and js`. Does that mean we'll need to create a `.cz.toml` in the subdirectory?

Either way works for me. 👍 But we still have the problem of how are we going to handle the git tag? Maybe we could enforce different tag format for...

Hi, thanks for the suggestion! If we want to add the flag `--version-files`, I think maybe we can handle it [here](https://github.com/commitizen-tools/commitizen/blob/14b6c382ff96e37ba118ba1b75073b0d2313ee91/commitizen/commands/bump.py#L35) like other arguments and add it [here](https://github.com/commitizen-tools/commitizen/blob/14b6c382ff96e37ba118ba1b75073b0d2313ee91/commitizen/cli.py#L133).

The basic idea of the dataclass part is to make moving from `dict` to `dataclass` which might be clear. The main idea of this issue is to use named capture...

> Still I see some complications, for conventional commits how would you capture `BREAKING CHANGE` and `!` as breaking chagnes with a named group? I've tried a while ago with...

It seems we do not need to parse the message when we bump the project version. All we want to know is which version (i.e. `MAJOR`, `MINOR`, `PATCH`) to bump....

If you add `|` to your body (but not scope), it will be turned into a break line. This feature is not well documented at this moment. 

Yes, we definitely should improve the message. Thanks for your help 🙂 I'm not sure the idea of the quote is what we wanted. What is the expected behavior if...

I'm neutral to this one since multiple-line does not bother me at all recently haha. I'm curious whether there's tool that can help us make this `echo` behavior happen easier.