Skip to content

Configuring commitizen with uv - make "cz init" work with existing pyproject.toml #1361

Open
@waterworthd-cim

Description

@waterworthd-cim

Description

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.

Are there work-arounds for these issues?

Possible Solution

No response

Additional context

No response

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions