-
-
Notifications
You must be signed in to change notification settings - Fork 143
[17.0][MIG] purchase_product_pack: Migration to 17.0 #171
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
Conversation
5b6c260 to
31c2f69
Compare
7c7d755 to
a49aa9d
Compare
Michelle-RiveroM
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
100% Functional
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok Functional
|
This PR has the |
|
/ocabot migration purchase_product_pack |
|
Sorry @antonyht27 you are not allowed to mark the addon tobe migrated. To do so you must either have push permissions on the repository, or be a declared maintainer of all modified addons. If you wish to adopt an addon and become it's maintainer, open a pull request to add your GitHub login to the |
|
hello, situation case : when create a purchase order, but on the pack product, best is to check purchase.order.partner_id is in product.product.seller_ids Can you agree to this request ? |
|
Hello. I just realized that the merge has not been done so that the purchase_product_pack module appears in version 17, even though everything seems to be OK. Is there any problem with finishing the merge so that it can appear in the version 17 repository? |
|
There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. |
|
Hi @pedrobaeza any problems with this PR, do I need to change something? |
|
/ocabot migration purchase_product_pack It requires a review of a PSC or maintainer. Right now I'm not able to do it, sorry. |
|
There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. |
|
Hi @antonyht27 do you mind creating a new PR for this migration? We tested it and works fine |
Sure, I’ll create a new PR for this migration. Thanks for testing it! |
|
@christian-ramos-tecnativa re-uploaded in #235 |
No description provided.