-
### Is there an existing issue or pull request for this?
- [X] I have searched the existing issues and pull requests
### Feature description
The current configuration lacks clear structure. T…
-
Hey,
I am the maintainer of a Conventional Commits linter that is still in development[1] and I have a question around valid scopes.
I read the full specification[2] and for scopes it says.
`…
-
I made a breaking change recently and I want to add a reference back to the associated issue in the change note, however `conventional-commits-parser` will stop at the first line that contains a refer…
-
When you send a embed it adds a footer to it.
The posibility to get that removed would be great.
-
os: macOS 11.1
node: v12.13.1
npm: v6.12.1
# start
1. Install according to the documentation
```
npm install -g conventional-changelog-cli
```
2. Execute the command
```
cd project
conv…
-
In my company we used to use [ ] instead of ( ). Is there any way to change the symbol?
-
## CVE-2022-25883 - High Severity Vulnerability
Vulnerable Libraries - semver-7.3.5.tgz, semver-6.3.0.tgz, semver-5.7.1.tgz
semver-7.3.5.tgz
The semantic version parser used by npm.
Library home p…
-
## Description
Add extra options to check commit message style and also to fix incorrect messages.
## Use cases
I have versioning enabled on main branch, but it breaks if any of the commits d…
-
As noted in #234, types are not allowed to have dashes in their value.
In the case where an invalid type is encountered, a warning should be printed to the console informing the user that a commit …
-
When you merge a PR within Azure DevOps, a prefix (`Merged PR 12345:`) is added to the commit message unless you manually remove it for every PR, leading to commit messages like:
```Merged PR 54123…