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][MIG] mail_activity_partner: Migration to version 16.0 #1156

Merged
merged 18 commits into from
Nov 17, 2023

Conversation

polqubiq
Copy link
Contributor

@polqubiq polqubiq commented Jun 6, 2023

No description provided.

@hugo-cordoba
Copy link

Hello, check the name of the PR. I think this migration corresponds to the module 'mail_activity_partner' not to the module 'product_pricelist_margin' :)

@polqubiq polqubiq changed the title [16.0][MIG] product_pricelist_margin: Migration to version 16.0 [16.0][MIG] mail_activity_partner: Migration to version 16.0 Jun 6, 2023
@polqubiq
Copy link
Contributor Author

polqubiq commented Jun 6, 2023

Hello, check the name of the PR. I think this migration corresponds to the module 'mail_activity_partner' not to the module 'product_pricelist_margin' :)

Whoops, you're absolutely right. Well seen! Thank you.

Copy link

@dariodelzozzo dariodelzozzo left a comment

Choose a reason for hiding this comment

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

Code Review

@simahawk
Copy link
Contributor

/ocabot migration mail_activity_partner

@simahawk
Copy link
Contributor

@polqubiq looks good, tnx. Just one nitpicking step if is possible for you: could you please amend the last commit to be [16.0][MIG] <module>: Migration to 16.0? You can see a similar commit for 15.0.

See guidelines https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-16.0#how-to

@polqubiq polqubiq force-pushed the 16.0-mig-mail_activity_partner branch from 54a5271 to 15490e0 Compare November 17, 2023 08:59
@polqubiq
Copy link
Contributor Author

polqubiq commented Nov 17, 2023

@polqubiq looks good, tnx. Just one nitpicking step if is possible for you: could you please amend the last commit to be [16.0][MIG] <module>: Migration to 16.0? You can see a similar commit for 15.0.

See guidelines https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-16.0#how-to

@simahawk I think it's not [16.0][MIG] <module>: Migration to 16.0. It is [MIG] $module: Migration to 16.0 instead. I've just made the change. Thanks!

@simahawk
Copy link
Contributor

@simahawk I think it's not [16.0][MIG] <module>: Migration to 16.0. It is [MIG] $module: Migration to 16.0 instead. I've just made the change. Thanks!

image

The odoo version can be there when is a migration 😉

/ocabot merge nobump

@OCA-git-bot
Copy link
Contributor

On my way to merge this fine PR!
Prepared branch 16.0-ocabot-merge-pr-1156-by-simahawk-bump-nobump, awaiting test results.

@simahawk
Copy link
Contributor

FTR tests were red because of our servers issue. Should be fixed now.

@OCA-git-bot OCA-git-bot merged commit 5e967be into OCA:16.0 Nov 17, 2023
2 of 4 checks passed
@OCA-git-bot
Copy link
Contributor

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

@polqubiq
Copy link
Contributor Author

@simahawk I think it's not [16.0][MIG] <module>: Migration to 16.0. It is [MIG] $module: Migration to 16.0 instead. I've just made the change. Thanks!

image

The odoo version can be there when is a migration 😉

/ocabot merge nobump

I thought that one thing is the name of the pull request and another is the name of the commit 🙃

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.