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] base: avoid ignoring right translations #4667

Merged
merged 1 commit into from
Jan 22, 2025

Conversation

chienandalu
Copy link
Member

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

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 chienandalu force-pushed the 16.0-fix-to_translate-terms branch from 14631e8 to dffd75a Compare November 18, 2024 13:49
@pedrobaeza pedrobaeza added this to the 16.0 milestone Nov 18, 2024
@pedrobaeza
Copy link
Member

@MiquelRForgeFlow
Copy link
Contributor

Could you rebase? Error is solved.

@pedrobaeza
Copy link
Member

Let's use ocabot for that:

/ocabot merge nobump

@OCA-git-bot
Copy link
Contributor

What a great day to merge this nice PR. Let's do it!
Prepared branch 16.0-ocabot-merge-pr-4667-by-pedrobaeza-bump-nobump, awaiting test results.

@OCA-git-bot OCA-git-bot merged commit 227c325 into OCA:16.0 Jan 22, 2025
1 of 2 checks passed
@OCA-git-bot
Copy link
Contributor

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

@pedrobaeza pedrobaeza deleted the 16.0-fix-to_translate-terms branch January 22, 2025 12:33
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.

4 participants