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

[17.0][MIG] res_partner_operating_unit: Migration to 17.0 #678

Merged
merged 16 commits into from
Jul 19, 2024

Conversation

yankinmax
Copy link

@yankinmax yankinmax commented Jun 4, 2024

Copy link

@vvrossem vvrossem left a comment

Choose a reason for hiding this comment

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

I have a doubt regarding the usage of Command.set instead of Command.link, unless using '4' in the first place was wrong,

res_partner_operating_unit/models/res_users.py Outdated Show resolved Hide resolved
res_partner_operating_unit/models/res_users.py Outdated Show resolved Hide resolved
@yankinmax yankinmax force-pushed the 17.0-mig-res_partner_operating_unit branch 2 times, most recently from 3081bde to f7a8126 Compare June 7, 2024 04:58
@yankinmax yankinmax force-pushed the 17.0-mig-res_partner_operating_unit branch from 2b58f03 to 294ba6d Compare June 11, 2024 13:46
Copy link

@Camille0907 Camille0907 left a comment

Choose a reason for hiding this comment

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

Technically LGTM :)

@yankinmax yankinmax force-pushed the 17.0-mig-res_partner_operating_unit branch from 294ba6d to 0bade30 Compare June 25, 2024 16:14
.pre-commit-config.yaml Outdated Show resolved Hide resolved
res_partner_operating_unit/models/res_partner.py Outdated Show resolved Hide resolved
@yankinmax yankinmax force-pushed the 17.0-mig-res_partner_operating_unit branch from 0bade30 to 59a24c7 Compare June 28, 2024 10:10
@yankinmax yankinmax force-pushed the 17.0-mig-res_partner_operating_unit branch 2 times, most recently from f2cba3d to a8a1ca1 Compare July 8, 2024 18:33
Copy link

@epanisset epanisset left a comment

Choose a reason for hiding this comment

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

[False issue]

@yankinmax
Copy link
Author

@epanisset so we leave the current state?

@yankinmax yankinmax force-pushed the 17.0-mig-res_partner_operating_unit branch from a8a1ca1 to 653b55f Compare July 9, 2024 13:43
@epanisset
Copy link

@epanisset so we leave the current state?

what do you mean?

@yankinmax yankinmax force-pushed the 17.0-mig-res_partner_operating_unit branch from a499690 to 73a76a7 Compare July 9, 2024 16:57
@yankinmax
Copy link
Author

@gurneyalex PR is updated with your suggestions and checked functionally.
Can you trigger merge please?

@gurneyalex
Copy link
Member

/ocabot merge nobump

@OCA-git-bot
Copy link
Contributor

On my way to merge this fine PR!
Prepared branch 17.0-ocabot-merge-pr-678-by-gurneyalex-bump-nobump, awaiting test results.

@gurneyalex
Copy link
Member

/ocabot migration res_partner_operating_unit

@OCA-git-bot OCA-git-bot added this to the 17.0 milestone Jul 19, 2024
@OCA-git-bot OCA-git-bot mentioned this pull request Jul 19, 2024
16 tasks
@OCA-git-bot OCA-git-bot merged commit a2fdbb4 into OCA:17.0 Jul 19, 2024
6 of 7 checks passed
@OCA-git-bot
Copy link
Contributor

Congratulations, your PR was merged at c3a9552. 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
Projects
None yet
Development

Successfully merging this pull request may close these issues.