René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Review Exit codes before v5 release (if possible)","articleBody":"### Description\n\nSome questions about exit codes were raised while I was reviewing our document.\n\n1. The current description of `NotAllowed` is \n\n```\n`--incremental` cannot be combined with a rev_range\n```\n\nBut now we use `NotAllowed` for other scenarios as well. It's a bit outdated.\n\n2. What is the difference among `InvalidCommandArgumentError`, `InvalidConfigurationError`, `NotAllowed`? I guess we need to clarify the usages.\n  - One of possible solutions may like giving them better, for example `UnknownCommandArgument`, `UnknownConfigurationFileFormat`. The word \"invalid\" has a lot of possible interpretations and it is very likely to be misused.\n\n3. `InvalidManualVersion` sounds like a kind of `InvalidCommandArgumentError`\n4. We have to add docstrings to those exceptions to reduce the possibility of misuse or abuse of exceptions. It would be even better if there is a tool to update the content of `docs/exit_code.md` whenever there is an update in `exceptions.py`\n\nhttps://github.com/commitizen-tools/commitizen/blob/master/commitizen/exceptions.py\n","author":{"url":"https://github.com/bearomorphism","@type":"Person","name":"bearomorphism"},"datePublished":"2025-11-20T15:42:47.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/1661/commitizen/issues/1661"}