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
Actually the only supported location for the config file .cz.* is the root folder of the project (according to the docu).
It would be great to have the following additional configuration levels also:
global (per user, for all projects)
system (for all users on this system)
The reason behind the request is that we don't need fullfledged conventional commits (scope e.g. can be skipped) and would like to customize it, but don't want to have the same cz.* config file in every repo on the system.
Actually we use commitizen mainly for properly formated commit messages.
Possible Solution
The actual code already has a list of configuration file names (defaults.py) and a list of cfg_warch_paths (config/init.py). Therefore it should not be to hard to add a global (user) directory and a system wide directory for searching too (at least with my limited pyhton knowledge).
Additional context
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Description
Actually the only supported location for the config file .cz.* is the root folder of the project (according to the docu).
It would be great to have the following additional configuration levels also:
The reason behind the request is that we don't need fullfledged conventional commits (scope e.g. can be skipped) and would like to customize it, but don't want to have the same cz.* config file in every repo on the system.
Actually we use commitizen mainly for properly formated commit messages.
Possible Solution
The actual code already has a list of configuration file names (defaults.py) and a list of cfg_warch_paths (config/init.py). Therefore it should not be to hard to add a global (user) directory and a system wide directory for searching too (at least with my limited pyhton knowledge).
Additional context
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: