René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Discussion: Clarify / standardize behavior for negative message_length_limit (should it require \u003e= 0?)","articleBody":"### Description\n\nI’d like to start a discussion about how `message_length_limit` should behave when it is set to a negative value.\n\nMy current thinking is that `message_length_limit` should be limited to non-negative integers (`\u003e= 0`), and that negative values should be rejected with an error.\n\nTo help explore this direction, I’ve also opened a PR: #1908 .\n\n### Steps to reproduce\n\n- `cz check -l -1 --message \"feat: hello\"`\n- `cz commit -l -1`\n\n### Current behavior\n\nnegative `message_length_limit` equals to no limit\n\n### Desired behavior\n\nI’d like to clarify the intended behavior and, if this matches the expected design, make it consistent:\n\n- `message_length_limit \u003c 0` raises an error.\n- `message_length_limit = 0` disables the length limit.\n- Leaving it unset in the CLI, or explicitly passing `None`, falls back to the config value consistently.\n\nIf maintainers prefer a different policy, I’d be happy to adjust the PR accordingly.\n\n### Screenshots\n\n_No response_\n\n### Environment\n\nCommitizen Version: 4.13.9\nPython Version: 3.14.3 (main, Feb  3 2026, 15:32:20) [Clang 15.0.0 (clang-1500.1.0.2.5)]\nOperating System: Darwin","author":{"url":"https://github.com/ttw225","@type":"Person","name":"ttw225"},"datePublished":"2026-03-20T04:13:49.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/1909/commitizen/issues/1909"}