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

[16.0][FIX] mail_composer_cc_bcc: adapt to changes upstream #1519

Merged

Conversation

hbrunn
Copy link
Member

@hbrunn hbrunn commented Dec 12, 2024

that's a nifty way to detect upstream changes and force adapting to it.

I wonder however if we couldn't achieve the same goal without copying so much code by setting some context keys that are picked up in an override of ir.mail.server#build_email

@OCA-git-bot
Copy link
Contributor

Hi @hailangvn2023,
some modules you are maintaining are being modified, check this out!

@nilshamerlinck
Copy link
Contributor

nilshamerlinck commented Dec 13, 2024

hi @hbrunn

@trisdoan
Copy link
Contributor

Hello @hbrunn, I just opened a PR: hbrunn#4 to add another changes from upstream, would you mind taking a look?

@hbrunn
Copy link
Member Author

hbrunn commented Dec 16, 2024

@trisdoan thanks, merged

@yajo
Copy link
Member

yajo commented Dec 16, 2024

Both the previous error message and the new changes are a bit cryptic... could you please explain what was happening?

emiliesoutiras added a commit to Groupe-Voltaire-SAS/social that referenced this pull request Dec 16, 2024
@hbrunn
Copy link
Member Author

hbrunn commented Dec 16, 2024

@yajo they created a test that compares the hash of the source code of a function they override with a list of known hashes, so as soon as this changes in upstream, the test fails and we know we have to check if we need to incorporate any changes from there.

Added an error message to this effect in f2e9624

@yajo
Copy link
Member

yajo commented Dec 16, 2024

Ah wow! That was very non-obvious. Thanks.

Would you mind to squash it and put that explanation in the commit message itself? I think it'll be valuable some day when it happens again and we git blame over it.

Apart from that, the change LGTM.

This is a test that compares the hash of the source code of a function they
override with a list of known hashes, so as soon as this changes in upstream,
the test fails and we know we have to check if we need to incorporate any changes
from there.
@hbrunn hbrunn force-pushed the 16.0-mail_composer_cc_bcc-fix-upstream-2024-12-12 branch from f2e9624 to 35e89eb Compare December 16, 2024 10:43
@hbrunn
Copy link
Member Author

hbrunn commented Dec 16, 2024

added the commit message. But what do you want me to squash here? Seems like three logically independent changes to me

Copy link
Member

@yajo yajo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the commits said something like "adapt to changes upstream. Changes in odoo/odoo#123123 made the hash change", their messages would be more valuable.

If a single commit contained all those explanation, that'd be equally good to me.

But in any case, it's OK if you don't prefer to squash. At this point it's good enough to me. 😄

Thank you very much!

/ocabot merge patch

@OCA-git-bot
Copy link
Contributor

This PR looks fantastic, let's merge it!
Prepared branch 16.0-ocabot-merge-pr-1519-by-yajo-bump-patch, awaiting test results.

@OCA-git-bot OCA-git-bot merged commit 0678011 into OCA:16.0 Dec 16, 2024
9 checks passed
@OCA-git-bot
Copy link
Contributor

Congratulations, your PR was merged at 695fc48. Thanks a lot for contributing to OCA. ❤️

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

Successfully merging this pull request may close these issues.

5 participants