-
-
Notifications
You must be signed in to change notification settings - Fork 281
cz check skip merge messages #483
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
commitizen skips "merge" automatically. we're working on make it configurable, but this is not available as of now. another way is to configure through https://commitizen-tools.github.io/commitizen/customization/ |
I'm talking of cz check this is an example of the commit message that bitbucket generates automatically:
` cz check returns a different value than 0. |
That's a bit weird as this should be skipped here. Could you please provide the version you test on? |
I'm checking why my "cz check" fails...thanks, I will report here.. |
ok, bitbucket merge commit is like: |
hmmm... interesting. I'm thinking of using re to check to support more format. @woile what do you think? |
I was not aware of this check, I think is worth adding |
can I create pull request adding pull request to the list? |
@manang Yes, that would be most appreciated. Many thanks! |
Hi, can you tell me why my pull request fails? |
I understood the problem, thanks |
no, I don't understand, there is an error outside the part that I changed. |
how long do you need to create the debian package with the correction of cz? |
We do not maintain a debian package afaik. The installation methods are listed here: https://commitizen-tools.github.io/commitizen/#installation Looking at them, I'm thinking we should review them. Probably nowadays is best to use something like |
ah, it is true...thanks a lot for your support |
Hi, is it possible to skip the check of messages like "merge branch"
So, the idea is that I want to skip the check of messages that match a regex.
Thanks
The text was updated successfully, but these errors were encountered: