[Feature Request] add `confirmCommit` in `skipQuestions`

[FatehAK]

✅ Checklist

• I am using the latest version
• 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

[Zhengqbbb]

https://cz-git.qbb.sh/config/engineer#skipquestions

Not include confirmCommit

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

causes vim to open. Is git hook prepare-commit-msg mode ?

[FatehAK]

Yes but I tried it without prepare-commit-msg hook as well, by running czg directly but still I got

[info]>>>: Commit has been canceled.

[Zhengqbbb]

Yes but I tried it without prepare-commit-msg hook as well, by running czg directly but still I got

[info]>>>: Commit has been canceled.

Not get yes default cancel.

I don't think this step should be skipped. This step is the last step to check the modification and repent. If you are sure, you can submit it directly. can you tell me what you need

[FatehAK]

Just thought of skipping that step can make committing faster. Since git shows the commit message at the end of committing anyway. If any changes in commit message (happens rarely) we could always amend the commit.

[Zhengqbbb]

ok if you considered faster. Can use regular alias definitions, like git czg :<alias>
But if you use interactive, that means you really have to seriously write commit

[Zhengqbbb]

like https://github.com/Zhengqbbb/qbb.sh/blob/main/.czrc
https://cz-git.qbb.sh/recipes/alias

[FatehAK]

Aliases won't work in my scenario since all commits in the repo are husky lint-staged driven.

But I agree on the seriousness part in interactive mode, just thought to avoid an enter key press again if dev knows what they have typed.

[Zhengqbbb]

I have finished and released the next(⭐️1.4.1-beta.1⭐️) version, you can use it first
npm install -D czg@next and npm install -D cz-git@next

I expect to merge main and release in the weekend, you can use it first, and give feedback in time if there is any problem.