René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"MAJOR,MINOR,PATCH config that takes in consideration the branch","articleBody":"### Description\n\nFirst of all, thank you for this program. I really enjoy using it.\n\nI looked for a way to perform what I need but I was not able to find the necessary information, therefore I suspect this is not something possible at the moment, ence, the feature request.\n\nI am currently using commitizen on projects in which:\n\n- main branch accept only major and minor\n- release branches that accept only patch (no breaking changes are allwed during patch fixes)\n\nAt the moment this is handled manually, the user needs to check which version will be issued and manually specify the version or correctly manage the commit name in order to obtain the right next-value.\n\nproblem is I won't trust who is performing the tag to make the correct tag. I would like to have it automated and enforced at configuration level.\n\nThank you for reading.\nHope this could be something interesting\n\n### Possible Solution\n\nI would like to be able to write in the config file something like:\n\nmin_value = [\n \"main\": \"minor\",\n\"release/*\": \"patch\"\n]\nmax_value = [\n\"main\": \"major\",\n\"release/*\": \"patch\"\n]\n\nThis will allow to cherry pick a fix and perform the bump without editing the commit message, or without specify the wanted increment on the command line.\n\n\n\n### Additional context\n\n_No response_\n\n### Related issues\n\n_No response_","author":{"url":"https://github.com/andyinno","@type":"Person","name":"andyinno"},"datePublished":"2025-08-08T07:08:50.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/1572/commitizen/issues/1572"}