-
Notifications
You must be signed in to change notification settings - Fork 934
[Question] how to extend and override config-conventional settings #2232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hey @padamstx , have a look at the docs here: https://commitlint.js.org/#/reference-configuration?id=configuration
Try to overwrite the specific rule like this but using the rule you want to overwrite: Hope this helps. Let us know if you need further help. |
Just to close the loop on this, I finally got around to using this info to modify our commitlint config.
I initially had the first line coded like this:
which is what was specified in the example Configuration object Anyway, thank you for the info @escapedcat ! |
Uhm, yeah, that's typescript, but the docs say |
…onventional-changelog#2424) * docs: show config example in ts and js conventional-changelog#2232 * docs: import config type from types conventional-changelog#2232
Hi, this is just a simple usage question.
I currently define a .commitlintrc.yml file with the following contents:
Currently, this commit message (
feat(CLI): add annotation for the flag name for a parameter/property in the CLI
) fails commitlint validation with error:scope must be lower-case [scope-case]
I'd like to relax this restriction to allow the component (i.e. "CLI") to be specified in upper case so that the above commit message passes validation.
Could someone please suggest how to configure that in my .commitlintrc.yml file?
Your Environment
commitlint --version
git --version
node --version
The text was updated successfully, but these errors were encountered: