Stack Overflow
Stack Overflow

Questions tagged [conventional-commits]

See the "Conventional Commits" specification homepage

40 questions
314
votes
2 answers

When to use "chore" as type of commit message?

What is the use of chore in semantic version control commit messages? Other types like feat or fix are clear, but I don't know when to use "chore". Can anyone provide a couple of examples of its use? Another maybe not related question: What's the…
Alireza Mirian
  • 5,862
  • 3
  • 29
  • 48
35
votes
2 answers

What would be a good commit message for updating package versions using Conventional Commits?

Following Conventional Commits what would be the best for commits regarding package version changes (upgrades/updates)? E.g.: feat: Bump React version to "16.13.1" E.g.: feat: Upgrade all dependencies
Gustavo Maximo
  • 4,426
  • 3
  • 17
  • 26
33
votes
5 answers

Semantic commit type when remove something

What semantic commit type is better to use, when I remove a feature: feat, refactor or something else?
Dmitry Druganov
  • 2,088
  • 3
  • 23
  • 32
19
votes
4 answers

Commit type before feature is done

Conventional Commits defines several types for commit messages like feat, fix, chore, ci etc. My question is about the workflow if I'm working on a feature whose scope spans several days of work. As a good developer I want to commit early and often…
Alexander Zeitler
  • 11,919
  • 11
  • 81
  • 124
13
votes
2 answers

Questions about conventional commit messages in git

I'm trying to adapt to conventional commit messages, described in this article. Here's a snippet from the article: Allowed values: feat (new feature) fix (bug fix) docs (changes to documentation) style (formatting, missing semi colons, etc;…
The.Wolfgang.Grimmer
  • 1,172
  • 2
  • 9
  • 32
12
votes
1 answer

semantic-release breaking-change using ! (exclamation mark)

Can Major version changes (aka Breaking Changes) be handled in semantic-release using the exclamation mark? git commit -m 'feat!: this is breaking, but is not recognized by semantic-release' Conventional Commit guidelines show that breaking changes…
David Cruwys
  • 6,262
  • 12
  • 45
  • 91
12
votes
2 answers

How to classify UI change according to the conventional commits specification?

Based on the conventional commits how are mere UI changes supposed to be classified? For example suppose a logout button is moved from the bottom of the screen to the top, an icon is added next to the text, and there is a new animation. Other then…
oidualc
  • 1,104
  • 1
  • 14
  • 21
11
votes
3 answers

How to run commitlint in GitHub workflow on every commit of a push

I have a Github repository, installed commitlint and husky locally and would like to setup a workflow running commitlint on every commit of a push when validating pull requests. On the main branch older commits are not following the conventional…
Question3r
  • 2,166
  • 19
  • 100
  • 200
7
votes
1 answer

How to ensure Master and Dev branches are kept in sync when deploying from CI/CD with Semantic Versioning or Lerna Publish

Setup I have several gitlab repos where the general setup involves having a master branch, a stage (pre-release) branch and a dev branch. Push permissions are disabled for all 3 branches. The workflow is to fork from the dev branch for any…
Daniel Mastrorillo
  • 151
  • 11
6
votes
1 answer

What should be the right "commit type" from conventional commit?

I created a commit with the purpose to unhide a feature, the code change is to only uncomment some lines of code and show the feature, so now the feature will be displayed to the user. Should this commit type be feat or chore? I think it should be…
João Niche
  • 63
  • 4
6
votes
1 answer

Many conventional commits of type feat on one feature branch

I've been added to a repo which uses semantic-release to automate bumping up the version of the NPM package. The repo uses the Conventional Commits specification and has a very limited README. If I was to create a feature/ABC-123 branch which…
JS_Dev
  • 427
  • 4
  • 14
5
votes
2 answers

Can Lerna bump prerelease version according to the Conventional Commits specification?

It doesn't seem that Lerna 3.20.2 is able to bump prerelease versions (e.g. 1.0.0-alpha.0) according to the Conventional Commits specification. I made a Minimal Reproducible Example if you want to try this out. Say we have two Lerna-managed…
customcommander
  • 17,580
  • 5
  • 58
  • 84
3
votes
1 answer

What would be a good commit type when adding more details to log statements (using Conventional Commits)

I added more detail to a log statement eg from logger.error('An error occurred') to logger.error('An error occurred for ${client.id}) what would be a good commit type to use under Conventional Commits?
tg0h
  • 575
  • 5
  • 17
3
votes
0 answers

lerna conventional versioning with github actions

I've setup the github actions to run on PRs against development and main. Then in the workflow I have a task as follow: if [ ${{ github.base_ref }} = development ]; then npx lerna version --conventional-prerelease --preid beta --yes else npx…
Jackson
  • 1,340
  • 3
  • 12
3
votes
1 answer

semantic commit message type for adding unit testing

Question : what semantic commit message type should i use for adding unit test cases? like Udin.test.js, feat , chore , or update ?
Blank
  • 61
  • 1
  • 3
1
2 3