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.
In some of the projects I'm working on, we work with custom commit types, which may not use all the default commit types in cocogitto, specifically the angular commit types. Currently, these default commit types cannot be disabled.
Describe the solution you'd like
I'd like to have the possibility of disabling any of the default commit types (besides fix and feat, as they are part of the Conventional Commits specification) in the configuration file. This could be as simple as:
[commit_types]
build = {}
What has to be kept in mind in the implementation of this is that users may want generated changelogs to include those commit types (of which the title may be custom) from the commit history, but just do not want future commits to be of that type. Perhaps a configuration property like active (boolean) would be fitting.
The text was updated successfully, but these errors were encountered:
I want to automate the release of cocogitto-action and cocogitto-bot along with cocogitto. Once this is done we should be ready for the next release. I don't have a lot of free time though, so I cannot give an exact date. But this should be soon.
Is your feature request related to a problem? Please describe.
In some of the projects I'm working on, we work with custom commit types, which may not use all the default commit types in cocogitto, specifically the angular commit types. Currently, these default commit types cannot be disabled.
Describe the solution you'd like
I'd like to have the possibility of disabling any of the default commit types (besides
fix
andfeat
, as they are part of the Conventional Commits specification) in the configuration file. This could be as simple as:What has to be kept in mind in the implementation of this is that users may want generated changelogs to include those commit types (of which the title may be custom) from the commit history, but just do not want future commits to be of that type. Perhaps a configuration property like
active
(boolean) would be fitting.The text was updated successfully, but these errors were encountered: