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
According to conventional commits, a breaking change can also be denoted by adding an exclamation mark (!) after type / scope.
This improves the visibility of breaking changes by making them visible in the commit message header.
fix(api)!: omit keys of undefined elements in JSON responses
BREAKING CHANGE: < reason here >
We started to take a look at Commitizen in combination with @digitalroute/cz-conventional-changelog-for-jira. Instead of contributing the feature there, I thought it would be more effective to contribute this feature "upstream" instead, as it has nothing to do with Jira.
Any thoughts about this? Are PRs welcome?
Thanks in advance for the great work so far!
The text was updated successfully, but these errors were encountered:
One alternative you can do until this is managed via commitzen is to use the -e option when committing
git cz -a -e
it will trigger the helper where you can select the types etc then when everything is done will open the commit message and allow you to edit it (via vim or other editor)- from there you can manually add the ! yourself
According to conventional commits, a breaking change can also be denoted by adding an exclamation mark (!) after type / scope.
This improves the visibility of breaking changes by making them visible in the commit message header.
We started to take a look at Commitizen in combination with
@digitalroute/cz-conventional-changelog-for-jira
. Instead of contributing the feature there, I thought it would be more effective to contribute this feature "upstream" instead, as it has nothing to do with Jira.Any thoughts about this? Are PRs welcome?
Thanks in advance for the great work so far!
The text was updated successfully, but these errors were encountered: