You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Hey, so we are using semantic-release to create our Github Releases using the following prefix table
I wanted to add BREAKING CHANGE: as a valid prefix because semantic-release uses it to create major/breaking releases but when I try it it just errors out.
But even after adding that it still errors out with:
Error: No release type found in pull request title "BREAKING CHANGE". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/
Available types:
- fix
- feat
- perf
- BREAKING CHANGE
Describe the solution you'd like
Be able to add BREAKING CHANGE as an acceptable prefix so we can use it together with this action
Describe alternatives you've considered
Using perf prefix that is accepted by the conventionalcommits but sometimes this doesn't reflect the type of change that we are introducing.
The text was updated successfully, but these errors were encountered:
Hmm, interesting. If you'd be interested in analyzing this and potentially setting up a PR, I'd be happy to review it. The only thing we document is that the types need to be newline-delimited:
# Configure which types are allowed (newline-delimited).# Default: https://github.com/commitizen/conventional-commit-typestypes: | fix feat
Is your feature request related to a problem? Please describe.
Hey, so we are using semantic-release to create our Github Releases using the following prefix table
I wanted to add BREAKING CHANGE: as a valid prefix because
semantic-release
uses it to create major/breaking releases but when I try it it just errors out.Example of configuration:
But even after adding that it still errors out with:
Describe the solution you'd like
Be able to add BREAKING CHANGE as an acceptable prefix so we can use it together with this action
Describe alternatives you've considered
Using
perf
prefix that is accepted by the conventionalcommits but sometimes this doesn't reflect the type of change that we are introducing.The text was updated successfully, but these errors were encountered: