You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Configuring commitizen with uv - make "cz init" work with existing pyproject.toml #1361
I'm evaluating commitizen as a simpler alternative to python-sematantic-release and other tools.
I've run into two issues, first the cz init command fails due to Config file pyproject.toml already exists - this is because I'm using uv which also has a uv init command - so once I've created my project using uv I don't appear to be able to intialise it for use with commitizen - is this the case or did I miss an something such as a cz init --force option?
Second, I use pre-commit to ensure with ruff etc to lint / format my code. This doesn't appear to integrate well with cz commit - i.e. if I stage changes, run pre-commit then cz commit everything is fine. If I forget to run pre-commit then I run the risk of losing everything I type (i.e. the commit message etc) because pre-commit may detect an issue which results in cz commit failing, losing everything I've typed.
changed the title [-]Configuring commitizen with uv[/-][+]Configuring commitizen with uv - make "cz init" work with existing pyproject.toml[/+]on Mar 20, 2025
Activity
Lee-W commentedon Mar 20, 2025
Hey @waterworthd-cim , sorry for the late reply.
I guess the first one is not yet supported, but it might be a valid feature 🤔 I usually do some copy-and-paste with these commands
For the second one, you can try
cz commit --retry.[-]Configuring commitizen with uv[/-][+]Configuring commitizen with uv - make "cz init" work with existing pyproject.toml[/+]bearomorphism commentedon Sep 19, 2025
I can take this one
bearomorphism commentedon Sep 19, 2025
Probably after #1601 is merged.