René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Add config option for line length warning (`-l/--message-length-limit`)","articleBody":"### Description\n\nIn issue #191, it was suggested to be able to add command line arguments to commitizen to ensure the correct line length, implemented in #1076. This was further updated in #1178  to allow the same argument to be used in `check` in addition to `commit`. \n\nExamples:\n\n    cz commit -l/--message-length-limit N\n\nor\n\n    cz check -l N -m MESSAGE\n\nHowever, the is not yet support in [config](https://commitizen-tools.github.io/commitizen/config/) or [customisation](https://commitizen-tools.github.io/commitizen/customization/) to add such a default argument without requiring the command line specification.\n\n### Possible Solution\n\nAn additional config option should exist in the configuration file to optionally define a commit line length.\nThis would then be utilised by both commitizen pre-commit [commit-msg, pre-push] hooks and command line invocations on the root directory of a project (i.e. with the relevant pyproject.toml for a python package).\n\n    pyproject.toml\n    \n    [tool.commitizen]\n    name = \"cz_customize\"\n    \n    [tool.commitizen.customize]\n      ... \n      message_length_limit = 72  # or l=72?\n    \nThen allowing the default parameter to propagate as follows:\n\n    cz commit\n    \u003e\u003e\u003e fails / succeeds depending on message length\n\n    cz check -m MESSAGE\n    \u003e\u003e\u003e fails / succeeds depending on message length\n\n\n\n### Additional context\n\n_No response_\n\n### Related issues\n\n_No response_","author":{"url":"https://github.com/mattgebert","@type":"Person","name":"mattgebert"},"datePublished":"2025-08-07T03:36:35.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/1571/commitizen/issues/1571"}