starraider / commitlint_config-typo3 Goto Github PK

View Code? Open in Web Editor NEW

0.0 0.0 0.0 47 KB

License: GNU General Public License v3.0

JavaScript 100.00%

commitlint_config-typo3's People

Contributors

Watchers

commitlint_config-typo3's Issues

[BUG] Rules for type-empty and subject-empty should be error

Describe the bug
Rules for type-empty and subject-empty are not working correctly. So they have to be set to level 0.

To reproduce
Steps to reproduce the behavior:

Open commitlint.confg.js in your editor
Set type-empty and subject-empty to level 2 (error)
Save the changes
Test: echo '[BUGFIX]: Foo bar' | npx commitlint

Expected behavior
'[BUGFIX]: Foo bar' is correct and should not through any error.

Application logs
⧗ input: [BUGFIX]: Foo bar
✖ subject may not be empty [subject-empty]
✖ type may not be empty [type-empty]

✖ found 2 problems, 0 warnings

[BUG] A colon (:) has to be put after the type for VSC extension

Describe the bug
The VS Code extension "VSCode Conventional Commits" always puts a colon ":" after the type. Therefore the pattern has to be changed accordently.

To reproduce
Steps to reproduce the behavior:

Install "VSCode Conventional Commits" in VSC
Commit a change and use a typ like [BUGFIX]
In the generated commit message there is always a colon after the typ, like [BUGFIX]:

Expected behavior
According to the TYPO3 documentation there should be no colon after the typ.

Recommend Projects