✅ Checklist

• [X] I am using the latest version
• [X] I have searched FAQ

📄 System Info

System:
    OS: macOS 12.6.1
    CPU: (8) arm64 Apple M1
    Memory: 966.95 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.12.1 - ~/Library/Caches/fnm_multishells/13083_1670507240516/bin/node
    Yarn: 1.22.19 - ~/Library/Caches/fnm_multishells/13083_1670507240516/bin/yarn
    npm: 9.1.3 - ~/Library/Caches/fnm_multishells/13083_1670507240516/bin/npm
    Watchman: 2022.11.28.00 - /opt/homebrew/bin/watchman
  npmPackages:
    czg: ^1.4.0 => 1.4.0

🔎 Description

Concise Description

I'm trying to skip the confirmCommit step by adding it to the skipQuestions array in .commitlintrc.js

skipQuestions: ['body', 'breaking', 'footerPrefix', 'footer', 'confirmCommit'],

But doing so causes vim to open with an empty commit message

Expected behavior

Should be able to skip the confirmCommit step. A commit should be made directly if we reach the end of the czg steps.

Steps to reproduce

Add 'confirmCommit' to the skipQuestions array

Screenshots or Screen Recording(if possible)

🔗 Reproduction link / repo:

No response

💭 Describe the feature

I would like to set the default issue prefix: Issues:. At the moment I can achieve that with:

    prompt: {
        issuePrefixs: [{ value: "Issues:", name: "default" }],
        customIssuePrefixsAlign: "bottom",
    }

but I would be anyway prompted to choose the ISSUES type.

I tried changing emptyIssuePrefixsAlias and customIssuePrefixsAlias to "", but with no effect.

I also tried skipQuestions: ["footerPrefix"], but then there's no prefix used at all.

💡 Proposed Solution

Additional boolean options similar to the Scopes one: allowCustomIssuePrefixs and allowEmptyIssuePrefixs and no prompt when there's only one issuePrefixs configured.

💭 Describe the feature

I have couple questions:

• What is diff betn. cz and czg
• When to use .commitlintrc.js and cz.config.js and Do I need to install extra packages in case of .commitlintrc.js?
• I've tried to use emoji-template as described but with cz.config.js in the root folder but the emojis are not showing in the CLI. I am using normal configs

  "config": {
    "commitizen": {
      "path": "node_modules/cz-git"
    }
  },

Thanks

💡 Proposed Solution

Appreciate all efforts in the documentation but this part needs to be clarified specially the part of czg

✅ Checklist

• [X] I am using the latest version
• [X] I have searched FAQ

📄 System Info

请求失败是不是将代码回退 ？

🔎 Description

Concise Description

请求失败是不是将代码回退 ？

Expected behavior

Steps to reproduce

Screenshots or Screen Recording(if possible)

🔗 Reproduction link / repo:

No response

💭 Describe the feature

Respect commitlint option about empty scopes by default, when there's no option set for cz-git explicitly:

  rules: {
    "scope-empty": [2, "never"]
  }

https://commitlint.js.org/#/reference-rules?id=scope-empty

💡 Proposed Solution

Fallback to commitlint config when the cz-git one is not specified directly.

If the commitlint setting is in the warning mode (1) instead of the error one (2), we could either ignore it or maybe provide some additional message.

💭 Describe the feature

We are using czg as part of husky's 'prepare-commit-msg' hook like so -

exec < /dev/tty && npx --no-install czg --hook || true

It works as expected but it open the vim editor unnecessarily at the end.

Is it possible to add a flag --no-edit so that the editor is not opened at the end?

💡 Proposed Solution

Add a preventEditorOpen flag which can be false by default and we can set it to true from .commitlintrc.js

If the preventEditorOpen flag is true then the git commit command will be git commit --no-edit

💭 Describe the feature

Is it possible to add a config for body-leading-blank option in commitlint?

💡 Proposed Solution

By setting an option bodyLeadingBlank to true in a config file, a new line will be added between commit subject and body.

💭 Describe the feature

• [x] add emojiAlign support emoji is placed before type
• [x] add alias to directly output the defined commit message

💡 Proposed Solution

Add emojiAlign

support emoji is placed before type The format alignment is really nice, but considering the validation with following Angular commit, the default is center

• type: "left" | "center" | "right"

Add alias

We may encounter commit messages that are often output, such as docs: fix typos, if we define like.

{
 "alias": {
     "df": "docs: fix typos"
  }
}

Usage:

1. czg :df
2. czg --alias="df"
3. cz_alias="df" git cz
4. cz_alias="df" cz

You can directly output docs: fix typos commit message It will be awesome and convenient.

💭 Describe the feature

I've been using commitizen-emoji for a while now, and found this library as a way to remove duplicated configs between commitzen and commitlint.

But, currently I see you only support the angular output; and with no clear way, in my testing, to replace or omit the type output.

the commit format I'm targeting is as follows:

<gitmoji>(<scope>): <subject>

scope being optional

Compared to Default Angular Commits <type>(<scope>): <subject>

Currently with cz-git I've managed to create commits like

feat: ✨ <subject>
feat(<scope>): ✨ <subject>

But I'm aiming for something like

✨ <subject>
✨ (<scope>): <subject>

💡 Proposed Solution

Enable users to customize their formatter with:

• sending their own custom function: receiving arguments corresponding to answers from the form view, and returning a string (title);
• implement a boolean argument conventionalFormat with default true, to enable the user to opt out of angular commit style

Example:

formatTitle.ts

export const formatTitle: FormatTitleType = ({ type, scope, subject }, config) => {
  const formattedScope = formatScopeOption(scope)
  const prelude = config.conventionalFormat
    ? `${type.emoji} ${type.name}${formattedScope}:`
    : `${type.emoji}${formattedScope ? ' ' + formattedScope + ':' : ''}`

  return `${prelude} ${subject}`
}

Example usage

const arguments = {
  type: {
    emoji: '✨',
    name: 'feat',
  },
  scope: 'mobile',
  subject: 'login screen'
}

console.log(formatTitle(arguments, {conventionalFormat: true}))  // ✨ feat (mobile): login screen
console.log(formatTitle(arguments, {conventionalFormat: false})) // ✨ (mobile): login screen

I believe there's some work to do on field type....type (ts typing) and fine-tuning, but I'm open to help in the conversation

💭 Describe the feature

Currently, when you provide the list of accepted scopes in the config, you select one in prompt by moving with arrows. The first scope highlighted is the first scope provided in the list. defaultScope option has no effect.

💡 Proposed Solution

My proposal would be to actually respect defaultScope, so that you can set its value to one of the accepted scopes and move it to the top of scopes list, so it becomes the first one proposed.

If the defaultScope value is not in the scopes list, we can ignore it / show some error.

💭 Describe the feature

commitlint provides support for multiple scopes: https://commitlint.js.org/#/concepts-commit-conventions?id=multiple-scopes

When you use @commitlint/cz-commitlint adapter, you can enable support for that in commitizen as well by providing the following options in commitlint config:

  prompt: {
    settings: {
      enableMultipleScopes: true
      scopeEnumSeparator: ","
    },
  }

https://commitlint.js.org/#/reference-prompt?id=settings

Then, you can select multiple scopes in commitizen with space and confirm with enter. If empty scopes are forbidden, if no scope is selected you get the hint you need to select at least one to continue.

💡 Proposed Solution

To respect the above configuration. The one issue I see is the fact that in cz-git space is used as input to search, but imho in that case we can "override" its behaviour to select the scope instead - scopes with spaces are rather rare use-case, so imho such a compromise should be quite acceptable. Or we can just think about another keystroke to trigger scope selection / unselection (right arrow to select, left arrow to unselect?).