-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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][MIG] sale_cancel_reason #2483
[16.0][MIG] sale_cancel_reason #2483
Conversation
(../trunk-generic/ rev 29.1.1)
(../trunk-generic/ rev 32.1.1)
(../trunk-generic/ rev 32.1.2)
- Update travis.yml to 8.0
Only hide button instead of renaming it
In order to get visibility on https://www.odoo.com/apps the OCA board has decided to add the OCA as author of all the addons maintained as part of the association.
… of sale_cancel_reason module
* [MIG] sale_cancel_reason Migration to 10.0 * Follow coding standard * Convert test to unittest2
Updated by Actualizar ficheiros PO com o novo POT (msgmerge) hook in Weblate.
Currently translated at 100.0% (23 of 23 strings) Translation: sale-workflow-10.0/sale-workflow-10.0-sale_cancel_reason Translate-URL: https://translation.odoo-community.org/projects/sale-workflow-10-0/sale-workflow-10-0-sale_cancel_reason/pt/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: sale-workflow-12.0/sale-workflow-12.0-sale_cancel_reason Translate-URL: https://translation.odoo-community.org/projects/sale-workflow-12-0/sale-workflow-12-0-sale_cancel_reason/
614404a
to
6b9d4ec
Compare
6b9d4ec
to
caa31db
Compare
43ca0b5
to
97ab626
Compare
hi @rousseldenis, could you check this code and merge this development? best regards |
/ocabot migration sale_cancel_reason |
Hi @pedrobaeza could you trigger the merge? Regards. |
/ocabot merge nobump |
This PR looks fantastic, let's merge it! |
Congratulations, your PR was merged at 2068a3a. Thanks a lot for contributing to OCA. ❤️ |
Next time, please check there are other PR open for the same module #2401 |
Hi @AaronHForgeFlow. I don't see that he had commented that he was migrating the module in the migration task #2215. To avoid this on future occasions, it is advisable when you start migrating a module, to add a comment in the migration task so that the rest of us know about it. Best regards! |
Sorry, I didn't check either. I usually look for other PRs before doing this, but this time was direct. |
No worries, it happened to me in the past too. BR. |
16.0 mig sale_cancel_reason