BUG: Breaking Change message can't be pushed

[dalisoft]

Expected 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)

1. Install commitlint and configuration

2. Try echo -e 'BREAKING CHANGE: baz' | yarn commitlint command

3. First step

4. 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

[escapedcat]

Thanks, how is this related to #313?

[dalisoft]

@escapedcat sorry, seems i misspelled or linked invalid related issue

[nerdgore]

Related to this issue: If you're using the exclamation mark in the subject to denote a breaking change the linting will also fail.

Works

echo -e 'feat(node): new feature (PROJ-123)' | yarn commitlint 

Fails

› echo -e 'feat(node)!: new feature (PROJ-123)' | yarn commitlint
⧗   input: feat(node)!: new feature (PROJ-123)
✖   subject may not be empty [subject-empty]
✖   type may not be empty [type-empty]
✖   references may not be empty [references-empty]

✖   found 3 problems, 0 warnings

[escapedcat]

This is somewhat related as well I guess: #2226

[AdeAttwood]

@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]

Will be published with the v13 release

[beamery-tomht]

v13 didn't fix it for me. #2226 (comment) this worked