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
I can see you're currently using angular's commit types (through npm package conventional-commit-types) and I think it would be a nice addition to add support for own commit types - either a config option like "additionalTypes" that would allow us to just add more types on top of the ones that are already in conventional-commit-types or a simple config option like "types" that would be used instead of conventional-commit-types.
Note that this isn't a request that requires you to support other conventional-changelog conventions and their different syntaxes, but just a request for an option that would allow people to extend already existing types with their own.
To add a little context, personally I would use this to add "enhance" type:
"enhance": {
"description": "A code change that improves current functionality",
"title": "Enhancements"
}
The text was updated successfully, but these errors were encountered:
amaury-tobias
added a commit
to amaury-tobias/cz-conventional-changelog
that referenced
this issue
Dec 20, 2019
I can see you're currently using angular's commit types (through npm package
conventional-commit-types
) and I think it would be a nice addition to add support for own commit types - either a config option like "additionalTypes" that would allow us to just add more types on top of the ones that are already inconventional-commit-types
or a simple config option like "types" that would be used instead ofconventional-commit-types
.Note that this isn't a request that requires you to support other conventional-changelog conventions and their different syntaxes, but just a request for an option that would allow people to extend already existing types with their own.
To add a little context, personally I would use this to add "enhance" type:
The text was updated successfully, but these errors were encountered: