generate defaults for cz_customize pyproject.toml

Description

I want to add a type but, in order to do so, I need to define the entire commitizen sections of my pyproject.toml as outlined here: https://commitizen-tools.github.io/commitizen/customization/.

It would be much easier to have the option to start with the defaults filled in (e.g. default questions, default message_template,etc...) and then modify from there. As it is now, I am copying values out of the ConventionalCommitsCz

Possible Solution

No response

Additional context

No response

Additional context

No response

What's in my mind was making cz_conventional_commits configurable and deprecate cz_customize? What do you think?

Yeah, that sounds good to me!

…

On Jul 22, 2022, at 8:14 AM, Wei Lee ***@***.***> wrote: What's in my mind was making cz_conventional_commits configurable and deprecate cz_customize? What do you think? — Reply to this email directly, view it on GitHub <#535 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABP2QC2WN5OBWM2RD7FRRXLVVK3FFANCNFSM52XGQHMA>. You are receiving this because you authored the thread.

Actually, thinking about it a bit more. I think that is good however, we’d still need to define all of the types, if we just wanted to add a type. So it would be good to have default config template to start from. Maybe that is what you are thinking?

…

On Jul 22, 2022, at 8:14 AM, Wei Lee ***@***.***> wrote: What's in my mind was making cz_conventional_commits configurable and deprecate cz_customize? What do you think? — Reply to this email directly, view it on GitHub <#535 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABP2QC2WN5OBWM2RD7FRRXLVVK3FFANCNFSM52XGQHMA>. You are receiving this because you authored the thread.

either way works for me. 🙂 we're kinda out of bandwidth these days. would be great if you're interested in sending a PR

@Lee-W

@Lee-W Hi, I would like to try and open a PR making cz_conventional_commits read from config and then fallback to defaults, allowing extensibility without the need to specify all configuration for cz_customize if we just want to override small behavior. Is that ok from your side?

feat(ConventionalCommitsCz): allow to override defaults from config

@Lee-W

@Lee-W I took the initiative and opened a PR. Hope it's ok and curios to hear your thoughts

@amitlevy21

Thanks @amitlevy21 . Will take a deeper look these days!

feat(ConventionalCommitsCz): allow to override defaults from config

@Lee-W

@Lee-W @amitlevy21
any updates to use cz_customize with default parser ?

No update at this moment. Would appreciate it if anyone wants to take a look 🙂

Anyone has the "[tool.commitizen.customize]" for .toml that match with conventional_commit pattern? I just want to make a small change :P

Navigation Menu

Repository navigation

generate defaults for cz_customize pyproject.toml #535

Description

Possible Solution

Additional context

Additional context

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

generate defaults for cz_customize pyproject.toml #535

Description

Description

Possible Solution

Additional context

Additional context

Activity

Lee-W commented on Jul 22, 2022

willjhenry commented on Jul 22, 2022

willjhenry commented on Jul 22, 2022

Lee-W commented on Jul 22, 2022

amitlevy21 commented on Aug 3, 2022

amitlevy21 commented on Aug 3, 2022

Lee-W commented on Aug 4, 2022

shantonio commented on Jun 26, 2023

Lee-W commented on Jun 27, 2023

Sherensberk commented on Apr 4, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions