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
So it is already playing quite nice with commitizen's config, meaning we don't need to have an extra .git-cz.json or changelog.config.js file in our repository, as all git-cz configs can be stored alongside with commitizen config in package.json.
However, when we want to use commitizen globally, the convention is to use .czrc or .cz.json file in $HOME directory, which isn't supported in git-cz.
So I'm wondering if we could do the same with package.json by also recursively reading .czrc and .cz.json like what commitizen does?
The text was updated successfully, but these errors were encountered:
Currently,
git-cz
already has its own configuration file resolution:git-cz/lib/getConfig.js
Lines 7 to 12 in e02bcb1
And also able to resolve
commitizen
config viaconfig.commitizen.changelog
inpackage.json
:git-cz/lib/getConfig.js
Lines 27 to 38 in e02bcb1
So it is already playing quite nice with commitizen's config, meaning we don't need to have an extra
.git-cz.json
orchangelog.config.js
file in our repository, as allgit-cz
configs can be stored alongside withcommitizen
config inpackage.json
.However, when we want to use
commitizen
globally, the convention is to use.czrc
or.cz.json
file in$HOME
directory, which isn't supported ingit-cz
.So I'm wondering if we could do the same with
package.json
by also recursively reading.czrc
and.cz.json
like whatcommitizen
does?The text was updated successfully, but these errors were encountered: