commitlint-config-git-commit-emoji
Shareable commitlint
config for the VS Code extension git-commit-plugin with emoji enabled.
Use with commitlint.
Getting started
npm install --save-dev @commitlint/cli commitlint-config-git-commit-emoji
echo "module.exports = {extends: ['git-commit-emoji']};" > .commitlintrc.js
Format
<emoji> <type>(<scope>): <subject>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>
Example
✨ feat(blog): add comment section
Rules
Problems
The following rules are considered problems for commitlint-config-git-commit-emoji
and will yield a non-zero exit code when not met.
Consult docs/rules for a list of available rules.
type-enum
- condition:
type
is found in value - rule:
always
- value
[
'🎉 init',
'✨ feat',
'🐞 fix',
'📃 docs',
'🌈 style',
'🦄 refactor',
'🎈 perf',
'🧪 test',
'🔧 build',
'🐎 ci',
'🐳 chore',
'↩ revert',
]
echo "foo: some message"
echo "🐞 fix: some message"
type-case
- description:
type
is in case value
- rule:
always
- value
'lowerCase'
echo "FIX: some message"
echo "🐞 fix: some message"
type-empty
- condition:
type
is empty - rule:
never
echo ": some message"
echo "🐞 fix: some message"
scope-case
- condition:
scope
is in case value
- rule:
always
'lowerCase'
echo "🐞 fix(SCOPE): some message"
echo "🐞 fix(scope): some message"
subject-case
- condition:
subject
is in one of the cases ['sentence-case', 'start-case', 'pascal-case', 'upper-case']
- rule:
never
echo "🐞 fix(SCOPE): Some message"
echo "🐞 fix(SCOPE): Some Message"
echo "🐞 fix(SCOPE): SomeMessage"
echo "🐞 fix(SCOPE): SOMEMESSAGE"
echo "🐞 fix(scope): some message"
echo "🐞 fix(scope): some Message"
subject-empty
- condition:
subject
is empty - rule:
never
echo "🐞 fix:"
echo "🐞 fix: some message"
subject-full-stop
- condition:
subject
ends with value
- rule:
never
- value
'.'
echo "🐞 fix: some message."
echo "🐞 fix: some message"
subject-exclamation-mark
- condition:
subject
must not have a !
before the :
marker - rule:
never
The angular commit
convention
dose not use a !
to define a breaking change in the commit subject. If you
want to use this feature please consider using the conventional commit
config.
- condition:
header
has value
or less characters - rule:
always
- value
72
echo "🐞 fix: some message that is way too long and breaks the line max-length by several characters"
echo "🐞 fix: some message"
body-leading-blank
- condition: Body should have a leading blank line
- rule:
always
echo "🐞 fix: some message
body"
echo "🐞 fix: some message
body"
- condition: Footer should have a leading blank line
- rule:
always
echo "🐞 fix: some message
BREAKING CHANGE: It will be significant"
echo "🐞 fix: some message
BREAKING CHANGE: It will be significant"
Thanks
License
MIT © Nor Cod