Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: option to prevent output input again #4255

Open
1 of 4 tasks
yoyoys opened this issue Jan 20, 2025 · 1 comment
Open
1 of 4 tasks

feat: option to prevent output input again #4255

yoyoys opened this issue Jan 20, 2025 · 1 comment
Labels

Comments

@yoyoys
Copy link

yoyoys commented Jan 20, 2025

Expected Behavior

> git -c user.useConfigOnly=true commit --quiet --allow-empty-message --file -
✖   type must be one of [build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test] [type-enum]

✖   found 1 problems, 0 warnings
ⓘ   Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint

Current Behavior

> git -c user.useConfigOnly=true commit --quiet --allow-empty-message --file -
⧗   input: featx: use commitlint instead of script
✖   type must be one of [build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test] [type-enum]

✖   found 1 problems, 0 warnings
ⓘ   Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint

Affected packages

  • cli
  • core
  • prompt
  • config-angular

Possible Solution

made a option to show problems only, this is good for vscode or ci tools.

Context

No response

@yoyoys yoyoys added the feature label Jan 20, 2025
@escapedcat
Copy link
Member

[...] this is good for vscode or ci tools

Can you elaborate how showing the message is an issue for vscode or ci tools? Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants