Expected Behavior
The following commit message should pass the footer-leading-blank rule:
test: footer-leading-blank bug
hello
see issue #1234
Current Behavior
The above commit message, however, fails with the following:
⧗ input: test: footer-leading-blank bug
⚠ footer must have leading blank line [footer-leading-blank]
⚠ found 0 problems, 1 warnings
ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint
This happens when the following conditions are true:
- The
# symbol is present in the commit body
- It is immediately followed by a number
- It is not at the beginning of a line
- It doesn't appear in the first line of the commit body
For instance, the following example, taken from the spec, also triggers this bug:
fix: correct minor typos in code
see the issue for details
on typos fixed.
Reviewed-by: Z
Refs #133
Affected packages
Steps to Reproduce
- Create a repo with the below config file
- In this repo, create a commit such as the above examples
- Run
commitlint --edit
- An error such as the above appears
commitlint.config.js
module.exports = {
extends: ['@commitlint/config-conventional'],
rules: {
'type-enum': [
1,
'always',
[
'build',
'chore',
'ci',
'docs',
'feat',
'fix',
'perf',
'refactor',
'revert',
'style',
'test'
]
]
}
}
Context
I was referencing a GitHub issue in the standard GitHub format, which is #1234. This was inside a very detailed commit message with multiple lines.
Your Environment
| Executable |
Version |
commitlint --version |
8.3.4 |
git --version |
2.20.1 |
node --version |
10.17.0 |
Expected Behavior
The following commit message should pass the
footer-leading-blankrule:Current Behavior
The above commit message, however, fails with the following:
This happens when the following conditions are true:
#symbol is present in the commit bodyFor instance, the following example, taken from the spec, also triggers this bug:
Affected packages
Steps to Reproduce
commitlint --editcommitlint.config.js
Context
I was referencing a GitHub issue in the standard GitHub format, which is #1234. This was inside a very detailed commit message with multiple lines.
Your Environment
commitlint --versiongit --versionnode --version