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
In the latest version of the conventional commits (1.0.0-beta.4) a new feature is added to define "breaking changes". It's still in beta but already released as specification-feature. This means we could add some new rules to validate this. We also have to update our type rules to make them play nice with this I guess.
We can modify the type-enum rule to only allow trailing !in this rule, or we can modify @commitlint/ensure to let it pass too. I prefer the first one because e.g. scopes should not have this functionality right?
Current Behavior
Affected packages
cli
core
prompt
config-angular
Possible Solution
Steps to Reproduce (for bugs)
Context
Your Environment
The text was updated successfully, but these errors were encountered:
Expected Behavior
In the latest version of the conventional commits (
1.0.0-beta.4) a new feature is added to define "breaking changes". It's still in beta but already released as specification-feature. This means we could add some new rules to validate this. We also have to update our type rules to make them play nice with this I guess.conventional-commits/conventionalcommits.org#134
Possible implementations
We can modify the
type-enumrule to only allow trailing!in this rule, or we can modify@commitlint/ensureto let it pass too. I prefer the first one because e.g. scopes should not have this functionality right?Current BehaviorAffected packages
Possible SolutionSteps to Reproduce (for bugs)ContextYour EnvironmentThe text was updated successfully, but these errors were encountered: