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

fix commit message for #693 #694

Closed
wants to merge 2 commits into from

Conversation

kobros-tech
Copy link

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

@pedrobaeza
Copy link
Member

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 pedrobaeza closed this Feb 5, 2025
@kobros-tech
Copy link
Author

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
What does "heldpesk" mean, then?

@pedrobaeza
Copy link
Member

Oh, you mean that... I though you were talking about the *. Well, doing a merge commit this way is not the solution. That only mangles the commit history, and we don't want that. They way to see the commits affecting a folder is to use the equivalent to https://github.com/OCA/helpdesk/commits/17.0/helpdesk_mgmt

@kobros-tech
Copy link
Author

Oh, you mean that... I though you were talking about the *. Well, doing a merge commit this way is not the solution. That only mangles the commit history, and we don't want that. They way to see the commits affecting a folder is to use the equivalent to https://github.com/OCA/helpdesk/commits/17.0/helpdesk_mgmt

does it mean we should keep it like that?

@kobros-tech
Copy link
Author

commits are affecting the module directory, no problem I saw an error and wanted to fix it.

best regards 🤍

@pedrobaeza
Copy link
Member

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.

@kobros-tech
Copy link
Author

@pedrobaeza
no worries
I guess, I am still able to fix it by getting the migration PR merged, right?

@pedrobaeza
Copy link
Member

Yeah, you can cherry-pick the commit and fix the commit message.

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

Successfully merging this pull request may close these issues.

4 participants