BUG: Breaking Change message can't be pushed
See original GitHub issueExpected Behavior
echo -e 'BREAKING CHANGE: baz' | yarn commitlint
yarn run v1.22.10
$ /Users/dalisoft/Desktop/Open_Source/nanoexpress/core/pro-slim/node_modules/.bin/commitlint
✨ Done in 0.50s.
Current Behavior
❯ echo -e 'BREAKING CHANGE: baz' | yarn commitlint
yarn run v1.22.10
$ /Users/dalisoft/Desktop/Open_Source/nanoexpress/core/pro-slim/node_modules/.bin/commitlint
⧗ input: BREAKING CHANGE: baz
✖ subject may not be empty [subject-empty]
✖ type may not be empty [type-empty]
✖ found 2 problems, 0 warnings
ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Affected packages
- cli
- core
- prompt
- config-angular
Possible Solution
It’s not solution, a like workaround, using any of valid enum before breaking change.
❯ echo -e 'fix(pkg): foo bar\n\nBREAKING CHANGE: baz' | yarn commitlint
yarn run v1.22.10
$ /Users/dalisoft/Desktop/Open_Source/nanoexpress/core/pro-slim/node_modules/.bin/commitlint
✨ Done in 0.50s.
Steps to Reproduce (for bugs)
-
Install
commitlint
and configuration -
Try
echo -e 'BREAKING CHANGE: baz' | yarn commitlint
command -
First step
-
Second step
commitlint.config.js
{
"extends": [
"airlight"
]
}
Context
Your Environment
Executable | Version |
---|---|
commitlint --version |
@commitlint/cli@11.0.0 |
git --version |
2.29.2 |
node --version |
v15.5.0 |
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Can't push to a new project in gitlab - commit message does ...
I have access to a repo which I don't administer but have full permissions I believe. It is only set up to use...
Read more >Git push rule Commit message blocking semantic release
Summary. We have setup a push rule on several repositories to enforce a commit message based on the Semantic Release commit message analyser. ......
Read more >Should behavioural changes be considered breaking ...
If bug fixes were considered breaking changes because they are a behavioural change, there would be a lot more major versions for libraries....
Read more >How can I edit / fix the last commit's message? - Tower Git Client
Simply put, this overwrites your last commit with a new one. This also means that you're not limited to just editing the commit's...
Read more >conventional commit messaging - Conventional Commits
A breaking change can be part of commits of any type. e.g., a fix: , feat: & chore: types would all be valid,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@escapedcat are we happy to get this one closed. For more info on the rule, you can refer to the angular config readme.
https://github.com/conventional-changelog/commitlint/tree/master/%40commitlint/config-angular#subject-exclamation-mark
@escapedcat sorry, seems i misspelled or linked invalid related issue