-
Notifications
You must be signed in to change notification settings - Fork 440
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
Make lower-casing of scope optional #94
Comments
According to the conventional-commits/conventionalcommits.org#24, the casing is not enforced and the only hard requirement is to be consistent. I could try to get a PR working if you're interested in adding a configurable option for this. |
I need to stick with v2 until this will be available since we need those uppercase letters at the front of the subject (because of reasons) :/ |
there is already a pull request for this #96 |
@ATLSAPI let me update and try it out. |
Looks like this doesn't work on Windows when using a global install as Node will grab the 3.0.1 install out of commitizen itself rather than the side-installed 3.1.0 cz-conventional-changelog, unless an explicit full path is used in .czrc |
So apart from that caveat (which is more of a Node and commitizen config issue) it looks like the functionality itself worked. Since providing an absolute path to cz-conventional-changelog in .czrc works, I'd say that this issue is good and done. Closing. |
Using cz-conventional-changelog with non-JS projects where components and file names may be cased is problematic due to the forced lower-casing of the value typed in for the scope prompt. Lower-casing should be optional, although defaulting to on is fine.
The text was updated successfully, but these errors were encountered: