[16.0][FIX] base: avoid ignoring right translations #4667
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
DBs with a long versions history could have right translations with wrong to_translate states. We should try to fix them in advance to avoid missing them. TT51774
chienandalu
force-pushed
the
16.0-fix-to_translate-terms
branch
from
14631e8 to
dffd75a
Compare
Member
|
The CI has been fixed in 17.0 this way: https://github.com/OCA/OpenUpgrade/pull/4669/files#diff-faff1af3d8ff408964a57b2e475f69a6b7c7b71c9978cccc8f471798caac2c88R88 |
Contributor
|
Could you rebase? Error is solved. |
Member
|
Let's use ocabot for that: /ocabot merge nobump |
Contributor
|
What a great day to merge this nice PR. Let's do it! |
Contributor
|
Congratulations, your PR was merged at 227c325. 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
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DBs with a long versions history could have right translations with wrong to_translate states. We should try to fix them in advance to avoid missing them.
cc @Tecnativa TT51774
please check @pedrobaeza