See the "Conventional Commits" specification homepage
Questions tagged [conventional-commits]
40 questions
0
votes
0 answers
Semantic commit type if only changed the error message
What is the best practice of semantic commit type if I just improved the output message to make it clearly?
Example:
Original output message is: console.log('You are wrong')
and I've changed into: console.log('You are wrong because "a" is…
Kurt
- 678
- 1
- 7
- 24
0
votes
0 answers
Can conventional changelog entry have more than one feature/bugfix item?
According to the conventional commits, only fix, feat or BREAKING CHANGE commits bumps version number. Following this specification, one may conclude that:
changelog version entry can't have "Features" (type feat) and "Bugfixes" (type fix) sections…
peetonn
- 2,942
- 4
- 32
- 49
0
votes
0 answers
Conventional Commits type for merge conflicts
According to the docs https://www.conventionalcommits.org/en/v1.0.0/ or to another extendable source if I have a merge conflict what a commit type should I use?
Stepan
- 67
- 8
0
votes
1 answer
How to create a branch from newest commits
Recently I faced a unique issue wherein I have to include only the newest commits in a branch discarding all the old ones.
e.g. consider I have such a commit structure:
[main branch]
af474e3 (HEAD -> main) Updated modal UI
c0f9599 Added modal UI …
bantya
- 576
- 11
- 23
0
votes
0 answers
Limiting conventional commits only to pull requests
As part of my CI/CD pipeline workflow, I am considering to make use of conventional commits to auto-generate release drafts in github. The idea of creating draft is to allow the code owners to review release notes before publishing it.
However, I am…
iamsmkr
- 800
- 2
- 10
- 29
0
votes
2 answers
Standard Version changelog repeats changes in different releases
I'm using standard-version with conventional commits to manage releases of an app i'm working on, and I'm having trouble with the auto generation of the Changelog.
Basically what happens is that every time I do a new release, it puts in the…
Matteo Carpi
- 522
- 6
- 23
0
votes
1 answer
error: Merge failed: Something went wrong during merge: 3:invalid byte sequence in US-ASCII. Please try again. on GitLab
Using GitLab
Received the following error message.
Merge failed: Something went wrong during merge: 3:invalid byte sequence in US-ASCII. Please try again.
solution to follow.
codeangler
- 779
- 8
- 16
-1
votes
1 answer
Prevent Lerna from making breaking version updates
I am looking for a way to restrict Lerna from major version updates during CI, as they will likely create dependency issues.
My intuition is to write an npm lifecycle script that executes upon version event. Still, I need clarification on what…
Maxim Kirilov
- 2,639
- 24
- 49
-1
votes
1 answer
Commit type according to convensional commit when resolving conflicts
I'm wondering what should be the commit type of a commit which resolves conflicts according to Convensional commits.
Please consider the following scenario
I'm in branch A
git merge B
resolve conflicts
add .
What should be the type of this commit…
Zero0
- 371
- 4
- 15
-1
votes
1 answer
Some references including examples for good "Git commit messages"
I need some references which include guidelines on having good git commit messages, its conventions and especially a few examples.
muel
- 43
- 1
- 13