In submitting a message, the scope usually represents the scope involved this time. There are usually two scopes here:

If you use monorepo's package as a scope, you can define it like this.

Of course, if you define the scope-enum using the commitlint rule, it will be automatically introduced.

Of course, if you want to add description information to the module scope customization, you can define it on the command line using the name and value properties.

If domestic users use Gitee as project management, then this tool can make good use of submitting messages to change the problem state.

Details: gitee submits related questions.

By setting the task status instruction, that is, the alias of the problem status change, by selecting the alias and entering the problem number, the problem can be well associated with management.

Automatically get questions related to submission. The release number of github is usually a number, but gitee is a bit anti-human, so that if I want to associate the release number every time I submit it, I need to copy and paste it in the branch name or look for it on the web page. If our branch name has a set of specifications, such as fix/issue_I72636_qb, I can handle it like this:

This is my sharing. I hope everyone will open their hearts and enjoy the process of exploring the configuration and make cli more suitable for you or your team. Welcome to share ~

My mental process of development:/post/706975825256

Link to original document:/zh//zh /zh/guide/recipes.html

Github address (welcome star): /Zhengqbbb/cz-git/cz-git