-
-
Notifications
You must be signed in to change notification settings - Fork 281
cz check fails #444
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
Comments
Do you mean commit like |
Hi @Lee-W , Thanks for your help |
somehow cz commit and cz check should match, I agree. there's not much information about the scope. I'm not a big fan of spaces but there shouldn't be anything wrong with them, the changelog would look ok as well: test config: changed parameter for foobar I've seen ppl using a |
Hello commit validation: failed! When I don't use the scope the check works well. This is my schema pattern config:
The scope supposed to be optional, isn't ? |
The problem was tat was missing (.*) after the first value: Example: @manang |
which version? on brew there is a version less recent. thanks |
v2.20.0 |
There was a problem during the publication to homebrew. So I can't test now.
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Carlos Bruno ***@***.***>
Sent: Friday, October 8, 2021 1:53:03 AM
To: commitizen-tools/commitizen ***@***.***>
Cc: Angelo Mantellini (manangel) ***@***.***>; Mention ***@***.***>
Subject: Re: [commitizen-tools/commitizen] cz check fails (#444)
v2.20.0
was released yesterday
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#444 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABNGJ2YJUFOFCGVTSPTJRATUFYXF7ANCNFSM5FOJ6C6Q>.
|
I've sent a PR to address homebrew publishing issue #445 Let's see whether this issue will be fixed. |
Closing as commitizen is being released on brew and apparently this issue was solved. Feel free to reopen if it still happens |
Description
cz check fails if the scope contains a space, but it is possible to commit with a space among the words.
Steps to reproduce
cz commit
->write a scope of two words with a space between
cz check --rev-range origin/master..
Current behavior
It fails, because the scope contains a space
Desired behavior
it does not show errors
Environment
Commitizen Version: 2.19.0
Python Version: 3.9.7 (default, Sep 3 2021, 12:37:55)
[Clang 12.0.5 (clang-1205.0.22.9)]
Operating System: Darwin (or ubuntu)
The text was updated successfully, but these errors were encountered: