Note: This may exist and just not be documented/be documented somewhere that I didn't look.
- Provide ability to pass a
--fix flag to the cli or config.fix: true | "prompt" | "auto-accept" in a config file.
- Provide option to create
config.rules.<rule name>.fix = null | () => {}
Expected Behavior
- Passing the flag or setting the property should cause commitlint to check rules that have the ability to be fixed automatically.
1.1. Can prompt the user to accept the change. (Could possibly add in functionality to always show prompt regardless of warnings or errors)
- Setting a
fix property inside of a custom rule sets the method for fixing said warning or error.
Current Behavior
The current behavior seems to just accept commits with warnings without any fixing capabilities.
Affected packages
Possible Solution
- alter current commit script to pipe into an additional script that applies a fix and/or prompts for confirmation
- alter core functionality to use a custom parser that generates a commitlint "AST"
Context
I just made a commit through commitizen that apparently didn't have an empty line before the footer, but commitlint accepted it with a warning.
Note: This may exist and just not be documented/be documented somewhere that I didn't look.
--fixflag to the cli orconfig.fix: true | "prompt" | "auto-accept"in a config file.config.rules.<rule name>.fix = null | () => {}Expected Behavior
1.1. Can prompt the user to accept the change. (Could possibly add in functionality to always show prompt regardless of warnings or errors)
fixproperty inside of a custom rule sets the method for fixing said warning or error.Current Behavior
The current behavior seems to just accept commits with warnings without any fixing capabilities.
Affected packages
Possible Solution
Context
I just made a commit through commitizen that apparently didn't have an empty line before the footer, but commitlint accepted it with a warning.