René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Add option for body line length","articleBody":"### Description\n\nTo allow for more granular control over commit message format, it would be useful if the line length of the commit body could be set. This should be settable from both the config or via a command line argument. \n\nI was hoping to use commitizen to enforce the 50/72 rule by setting those limits for the subject and body, without the need to customise. \n\nI found the `--message-length-limit` command line option and am excited to see that there is work being done in [#1574](https://github.com/commitizen-tools/commitizen/pull/1574) to add this to the config. However, this only affects the first line 'subject' of the message.\n\nTo be clear, the proposed option should affect the length of each line in the commit body, not the total length of the body.\n\n### Possible Solution\n\nA new config option would be introduced that allows the maximum line length of the commit message body to be set. Suggested, descriptive config option name:\n\n`body-line-length-limit`\n\nThe existing `message_length_limit` option could be renamed to more explicitly describe its effect and to align the naming of the two options, becoming:\n\n`subject-length-limit`\n\nThe corresponding command line versions would become:\n\n`--body-line-length-limit`\n\nand\n\n`--subject-length-limit`\n\nThe short option `--l` would be removed as it would appear ambiguous in this scenario.\n\n### Additional context\n\n_No response_\n\n### Related issues\n\nIn progress issue supporting the subject length being set by config [#1574](https://github.com/commitizen-tools/commitizen/pull/1574)","author":{"url":"https://github.com/andrewmaudsley","@type":"Person","name":"andrewmaudsley"},"datePublished":"2025-09-12T17:06:46.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":10},"url":"https://github.com/1597/commitizen/issues/1597"}