Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork304
-
newbie to commitizen. I chose all the default values when I tried to install commitzen via homebrew. 2 questions:
i chose |
BetaWas this translation helpful?Give feedback.
All reactions
I have decided the following:
- am i adding dependency or udpating or removing dependency? if so, then the verb is "add", "update", "remove" respectively
- the type will depend if the dependency changes behavior detected by the user. if so then it's a feat or fix. if it doesn't, then it's a refactor/build/ci depending on the dependency scope
Thank you. I needed this discussion to help me think.
Replies: 1 comment 7 replies
-
I think it's fine. What you have to keep in mind is that ci is ignored by commitizen. When you want a version to be bumped most of the time you have to use |
BetaWas this translation helpful?Give feedback.
All reactions
-
What I mean is if I were to add dependency or simply update the dependency What type do I choose (feat,fix,refactor,etc)? Esp since commitizen default list of choices does not contain "chore" |
BetaWas this translation helpful?Give feedback.
All reactions
-
First, you don't need to use For choosing a type, is up to you, there are 2 philosophies:
|
BetaWas this translation helpful?Give feedback.
All reactions
-
I agree that I don't always have to use cz commit But I like how cz makes it clear with a menu for me to choose So as much as I can, I like to keep within the menu That's my motivation for this discussion thread |
BetaWas this translation helpful?Give feedback.
All reactions
-
I have decided the following:
Thank you. I needed this discussion to help me think. |
BetaWas this translation helpful?Give feedback.
All reactions
-
No problem, also don't be too rigid, if with time this doesn't work for you, evaluate again, and create new guidelines. Good luck! |
BetaWas this translation helpful?Give feedback.
All reactions
👍 1