René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Using --allow-no-commit on bump doesn't work (when updating CHANGELOG)","articleBody":"### Description\n\n- python: 3.13.2\n- commitizen: 4.13.7\n\n```\n[tool.commitizen]\nname = \"cz_customize\"\nversion_provider = \"pep621\"\nversion_scheme = \"semver2\"\nannotated_tag = true\nupdate_changelog_on_bump = true\nchangelog_merge_prerelease = true\nprerelease_offset = 1\npre_bump_hooks = [\"./add-issue-links-to-changelog.sh\"]\n```\n\nIt seems that I am unable to **bump** if there are no changes _and_ I want to update the CHANGELOG. In spite of attempting to ignore the fact there are no changes by using `--allow-no-commit`, when I try and produce a new pre-release (e.g. with `--prerelease rc`) I get **No commits found**.\n\nIf I do not set `update_changelog_on_bump = true` then it appears to work.\n\nBut it is perfectly reasonable to: -\n\n1. Create a new release when there are no changes in the repository (i.e. going from **beta** to **rc**)\n2. Also alter the **CHANGELOG** (to indicate there has been a release but nothing has changed)\n\nIn summary ... `--allow-no-commit` should perform as advertised ... allow a release regardless of changes.\n\n\u003e See discussion https://github.com/commitizen-tools/commitizen/discussions/1865\n\n### Steps to reproduce\n\nHere's my config `pyproject.toml` commitizen configuration: -\n\n```\n[tool.commitizen]\nname = \"cz_customize\"\nversion_provider = \"pep621\"\nversion_scheme = \"semver2\"\nannotated_tag = true\nupdate_changelog_on_bump = true\nchangelog_merge_prerelease = true\nprerelease_offset = 1\npre_bump_hooks = [\"./add-issue-links-to-changelog.sh\"]\n```\n\n### Bump a release (when there are changes, creating a beta release)\n\n```\ncz bump --allow-no-commit --prerelease beta`\n```\n\n\u003e Let's assume this creates `4.5.0-beta.5`\n\n### Do it again (for a release candidate)\n\n```\ncz bump --allow-no-commit --prerelease rc`\n```\nIn this case I get told...\n\n```\nbump: version 4.5.0-beta.5 → 4.5.0-rc.1\ntag to create: 4.5.0-rc.1\nincrement detected: PATCH\n\nNo commits found\n```\n\n\n### Current behavior\n\nI'm told **No commits found** even though I have used `--allow-no-commit`\n\n### Desired behavior\n\nUsing `--allow-no-commit` should never result in the error **No commits found**\n\n### Screenshots\n\n_No response_\n\n### Environment\n\nCommitizen Version: 4.13.7\nPython Version: 3.13.2 (v3.13.2:4f8bb3947cf, Feb  4 2025, 11:51:10) [Clang 15.0.0 (clang-1500.3.9.4)]\nOperating System: Darwin\n","author":{"url":"https://github.com/alanbchristie","@type":"Person","name":"alanbchristie"},"datePublished":"2026-02-11T12:51:24.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/1866/commitizen/issues/1866"}