-
-
Notifications
You must be signed in to change notification settings - Fork 334
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
fix commit message for #693 #694
Conversation
No, it's correct and it has been used a lot when you work in several modules at the same time. You should grep other way, or masking the Closing as no valid. |
@pedrobaeza |
Oh, you mean that... I though you were talking about the |
does it mean we should keep it like that? |
commits are affecting the module directory, no problem I saw an error and wanted to fix it. best regards 🤍 |
Yeah, thanks, but that provokes other side effects. Think that a lot of people is not caring too much about the commit messages, and well, typos may happen continuously and pass unnoticed in the review. That's why I recommend you to not use that way of checking changes in a module. |
@pedrobaeza |
Yeah, you can cherry-pick the commit and fix the commit message. |
The commit message for #693 is:
[17.0][IMP] heldpesk*: Update logos #693
which is syntactical incorrect and can not be shown in log using grep as a result.
the commit message should be:
[IMP] helpdesk_mgmt: Update Logo
This will be appended in the #676