Discuss `cz init` `self.config`

[bearomorphism]

Description

Just noticed this.

I consider it strange that self.config is widely referenced by Init object. In normal scenarios, there shouldn't be configuration files when user runs cz init?

Maybe we should replace those self.config references by DEFAULT_SETTINGS. wdyt?

The only case self.config should be used is to check whether the project is already initialized by cz.

Possible Solution

No response

Additional context

No response

Related issues

No response

[Lee-W]

1. Interface consistency

   commitizen/commitizen/cli.py

   Lines 109 to 178 in 0497ef2

   	"commands": [
   	{
   	"name": ["init"],
   	"description": "init commitizen configuration",
   	"help": "init commitizen configuration",
   	"func": commands.Init,
   	},
   	{
   	"name": ["commit", "c"],
   	"description": "create new commit",
   	"help": "create new commit",
   	"func": commands.Commit,
   	"arguments": [
   	{
   	"name": ["--retry"],
   	"action": "store_true",
   	"help": "retry last commit",
   	},
   	{
   	"name": ["--no-retry"],
   	"action": "store_true",
   	"default": False,
   	"help": "skip retry if retry_after_failure is set to true",
   	},
   	{
   	"name": "--dry-run",
   	"action": "store_true",
   	"help": "show output to stdout, no commit, no modified files",
   	},
   	{
   	"name": "--write-message-to-file",
   	"type": Path,
   	"metavar": "FILE_PATH",
   	"help": "write message to file before committing (can be combined with --dry-run)",
   	},
   	{
   	"name": ["-s", "--signoff"],
   	"action": "store_true",
   	"help": "Deprecated, use 'cz commit -- -s' instead",
   	},
   	{
   	"name": ["-a", "--all"],
   	"action": "store_true",
   	"help": "Tell the command to automatically stage files that have been modified and deleted, but new files you have not told Git about are not affected.",
   	},
   	{
   	"name": ["-e", "--edit"],
   	"action": "store_true",
   	"default": False,
   	"help": "edit the commit message before committing",
   	},
   	{
   	"name": ["-l", "--message-length-limit"],
   	"type": int,
   	"help": "length limit of the commit message; 0 for no limit",
   	},
   	{
   	"name": ["--"],
   	"action": "store_true",
   	"dest": "double_dash",
   	"help": "Positional arguments separator (recommended)",
   	},
   	],
   	},
   	{
   	"name": "ls",
   	"description": "show available commitizens",
   	"help": "show available commitizens",
   	"func": commands.ListCz,
   	},

2. commitizen/commitizen/commands/init.py

   Lines 79 to 82 in 0497ef2

   	def __call__(self) -> None:
   	if self.config.path:
   	out.line(f"Config file {self.config.path} already exists")
   	return

   we check whether there's already a config

[woile]

A feature I would like to see, which would require a specification first:

How to extend the init in your own custom rules? For example, I maintain this convention, and if the user chooses it in the init, then it should ask about the settings provided by the conventions:
https://github.com/kpn/cz-kpn?tab=readme-ov-file#custom-configuration

So the convention, should be able to provide its own "options" if it makes sense

[Lee-W]

like what @woile proposed