commitizen/conventional-commit-types

Suggestion - add ver / version

premanshup opened this issue · 5 comments

premanshup commented

Sometimes we commit with just the version change. I think just changing version number does not fall under either fix or feat. So I feel like we should have a separate ver for just version changes?

MarkWithall commented

We use release for a version change, as the two tend to coincide.

premanshup commented

@MarkWithall Thank you for the suggestion but looking at the JSON file https://github.com/commitizen/conventional-commit-types/blob/master/index.json I did not find release anywhere. Are there any plans of adding release in the check?

MarkWithall commented

I've seen others use chore(release) (e.g. https://github.com/matatk/landmarks/commits/master), so it's possible that our use of release comes from a mis-translation of that. There's a certain sense in keeping the set of types minimal.

  • 👍1
premanshup commented

@MarkWithall I see, we can use something similar to the eg which you have shared. Thank you! I'm closing this issue.

  • 👍1
AndersDJohnson commented

Yes, chore(version): or chore(release): is recommended here.