René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Configuring commitizen with uv - make \"cz init\" work with existing pyproject.toml","articleBody":"### Description\n\nI'm evaluating commitizen as a simpler alternative to python-sematantic-release and other tools. \n\nI'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?\n\nSecond, 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.\n\nAre there work-arounds for these issues? \n\n### Possible Solution\n\n_No response_\n\n### Additional context\n\n_No response_\n\n### Additional context\n\n_No response_","author":{"url":"https://github.com/waterworthd-cim","@type":"Person","name":"waterworthd-cim"},"datePublished":"2025-03-01T01:51:16.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/1361/commitizen/issues/1361"}