Wei Lee
Maybe we could make the encoding configurable?
Hi @adam-grant-hendry we've release a new version of commitizen. Could you please try whether 2.30.0 solve this issue?
Hi @adam-grant-hendry , I notice you create another issue regarding to it. If pre-commit does not work, could you please use `git commit ... --no-verify` and `git push ... --no-verify`...
It would be even more helpful if you could document this on the doc for windows users. Thanks!
Step 1 and 2 is done by #156
If any configuration not supported by commitizen exists in the section `[tool.commitizen]`, any commtizen command should fail with an error message saying which configuration is not supported. Days ago, I...
I like @alecgerona 's idea more haha. We might be able to change it here. https://github.com/commitizen-tools/commitizen/blob/master/commitizen/commands/commit.py#L76 We can still output the error from git
I think it a great idea. But one of the problems we'll encounter is whether decli/argparse supports this kind of parsing.
The methods in this discussion look promising. https://stackoverflow.com/questions/25864774/how-to-read-the-remaining-of-a-command-line-with-argparse
Not sure whether this will work https://docs.python.org/3/library/argparse.html#argparse.ArgumentParser.parse_known_args. But it might still not be able to handle arguments that's too complicate (e.g., `--unknown-arg arg-1 arg-2`). I second the idea of `--`