Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[Solved] What type to choose to commit .cz.toml? #847

Answered by simkimsia
simkimsia asked this question in Q&A
Discussion options

newbie to commitizen. I chose all the default values when I tried to install commitzen via homebrew.

2 questions:

  1. when to use build vs ci?
  2. i commited .cz.toml and this is the commit message using commitizen
ci(.cz.toml): use conventional commits by way of commitizen

i chose ci but not sure if I am doing this correctly

You must be logged in to vote

I have decided the following:

  1. am i adding dependency or udpating or removing dependency? if so, then the verb is "add", "update", "remove" respectively
  2. 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

Comment options

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 fix or feat.
And remember the commit message usually ends up in the changelog, so you want to write something meaningful for the reader

You must be logged in to vote
7 replies
Comment options

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"

Comment options

First, you don't need to use cz commit, you can just do git commit -am "chore: add new dependency", but it will be ignored by the bump`.

For choosing a type, is up to you, there are 2 philosophies:

  1. Bump always: this means you'd use something like fix and feat all the time. When you install a new dependency it could be a dependency that fixes something. This is just simpler to think about: new commits -> new bump
  2. Bump sometimes: some dependencies may introduce fixes, or security updates, others might be just dev dependencies, so it's not necessary. In this case, you choose to ignore some changes, because they don't require a bump, but at the risk of making a mistake of pushing something that should've been a bump. I've had this a lot of times, specially with dependabot, which pushes a build for dependencies, and then people ask me if I can release the version manually, because they need either that new dep, or because the constrain in dependencies is a problem for them
Comment options

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

Comment options

I have decided the following:

  1. am i adding dependency or udpating or removing dependency? if so, then the verb is "add", "update", "remove" respectively
  2. 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.

Answer selected by simkimsia
Comment options

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants

AltStyle によって変換されたページ (->オリジナル) /