Skip to content

Conversation

@SirPyTech
Copy link

Backporting #3375.
@twalter-c2c and other participants to the linked PR @dreispt @grindtildeath @henrybackman you might be interested.

Could not manage to create a test for this, any suggestion is appreciated.

Copy link
Contributor

@francesco-ooops francesco-ooops left a comment

Choose a reason for hiding this comment

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

Functional ok!

@francesco-ooops
Copy link
Contributor

@dreispt can this be merged? thanks!

Copy link
Contributor

@twalter-c2c twalter-c2c left a comment

Choose a reason for hiding this comment

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

LGTM. I have no suggestion on how to add a generic test for this change, to be honest. I had a specific issue that was solved by this fix, but I would not use it as a test case scenario.

@francesco-ooops
Copy link
Contributor

@dreispt ping :)

@OCA-git-bot
Copy link
Contributor

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

@francesco-ooops
Copy link
Contributor

@OCA/tools-maintainers can this be merged? thanks!

@thomaspaulb
Copy link
Contributor

/ocabot merge patch

Does this need a forward port to other versions?

@OCA-git-bot
Copy link
Contributor

What a great day to merge this nice PR. Let's do it!
Prepared branch 14.0-ocabot-merge-pr-3492-by-thomaspaulb-bump-patch, awaiting test results.

@francesco-ooops
Copy link
Contributor

@thomaspaulb it's on 18, would make sense to have it on 16 and 17

@OCA-git-bot OCA-git-bot merged commit f7abe85 into OCA:14.0 Jan 20, 2026
9 checks passed
@OCA-git-bot
Copy link
Contributor

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

@thomaspaulb
Copy link
Contributor

If you have the time could you prepare the PRs

@francesco-ooops
Copy link
Contributor

@thomaspaulb will try :)

It would be good tho to be consistent on this and have a method to organize backportings as soon as original PRs are merged

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.

6 participants