-
Notifications
You must be signed in to change notification settings - Fork 4
Committing guide
Joao Maio edited this page Sep 6, 2021
·
2 revisions
Must be one of the following:
- build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
- ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
- docs: Documentation only changes
- feat: A new feature
- fix: A bug fix
- perf: A code change that improves performance
- refactor: A code change that neither fixes a bug nor adds a feature
- style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
- test: Adding missing tests or correcting existing tests
(from @commitlint/config-conventional)
Lint your conventional commits
Shareable commitlint
config enforcing conventional commits.
Use with @commitlint/cli and @commitlint/prompt-cli.
npm install --save-dev @commitlint/config-conventional @commitlint/cli
echo "module.exports = {extends: ['@commitlint/config-conventional']};" > commitlint.config.js
The following rules are considered problems for @commitlint/config-conventional
and will yield a non-zero exit code when not met.
Consult docs/rules for a list of available rules.
-
condition:
type
is found in value -
rule:
always
-
level:
error
-
value
[ 'build', 'ci', 'chore', 'docs', 'feat', 'fix', 'perf', 'refactor', 'revert', 'style', 'test' ];
echo "foo: some message" # fails
echo "fix: some message" # passes
-
description:
type
is in casevalue
-
rule:
always
-
level:
error
-
value
'lowerCase'
echo "FIX: some message" # fails
echo "fix: some message" # passes
-
condition:
type
is empty -
rule:
never
-
level:
error
echo ": some message" # fails
echo "fix: some message" # passes
-
condition:
scope
is in casevalue
-
rule:
always
-
level:
error
'lowerCase'
echo "fix(SCOPE): some message" # fails
echo "fix(scope): some message" # passes
-
condition:
subject
is in one of the cases['sentence-case', 'start-case', 'pascal-case', 'upper-case']
-
rule:
never
-
level:
error
echo "fix(SCOPE): Some message" # fails
echo "fix(SCOPE): Some Message" # fails
echo "fix(SCOPE): SomeMessage" # fails
echo "fix(SCOPE): SOMEMESSAGE" # fails
echo "fix(scope): some message" # passes
echo "fix(scope): some Message" # passes
-
condition:
subject
is empty -
rule:
never
-
level:
error
echo "fix:" # fails
echo "fix: some message" # passes
-
condition:
subject
ends withvalue
-
rule:
never
-
level:
error
- value
'.'
echo "fix: some message." # fails
echo "fix: some message" # passes
-
condition:
header
hasvalue
or less characters -
rule:
always
-
level:
error
- value
100
echo "fix: some message that is way too long and breaks the line max-length by several characters" # fails
echo "fix: some message" # passes
-
condition:
footer
should have a leading blank line -
rule:
always
- level:
warning
- value
100
echo "fix: some message
BREAKING CHANGE: It will be significant" # warning
echo "fix: some message
BREAKING CHANGE: It will be significant" # passes
-
condition:
footer
each line hasvalue
or less characters -
rule:
always
- level:
error
- value
100
echo "fix: some message
BREAKING CHANGE: footer with multiple lines
has a message that is way too long and will break the line rule 'line-max-length' by several characters" # fails
echo "fix: some message
BREAKING CHANGE: footer with multiple lines
but still no line is too long" # passes
-
condition:
body
should have a leading blank line -
rule:
always
- level:
warning
- value
100;
echo "fix: some message
body" # warning
echo "fix: some message
body" # passes
-
condition:
body
each line hasvalue
or less characters -
rule:
always
- level:
error
- value
100;
echo "fix: some message
body with multiple lines
has a message that is way too long and will break the line rule 'line-max-length' by several characters" # fails
echo "fix: some message
body with multiple lines
but still no line is too long" # passes