Skip to content

MAJOR,MINOR,PATCH config that takes in consideration the branch #1572

@andyinno

Description

@andyinno

Description

First of all, thank you for this program. I really enjoy using it.

I 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.

I am currently using commitizen on projects in which:

  • main branch accept only major and minor
  • release branches that accept only patch (no breaking changes are allwed during patch fixes)

At 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.

problem 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.

Thank you for reading.
Hope this could be something interesting

Possible Solution

I would like to be able to write in the config file something like:

min_value = [
"main": "minor",
"release/": "patch"
]
max_value = [
"main": "major",
"release/
": "patch"
]

This 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.

Additional context

No response

Related issues

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions