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] partner_contact_personal_information_page: Migration to version 17.0 #1608

Conversation

Daemo00
Copy link
Contributor

@Daemo00 Daemo00 commented Nov 18, 2023

No description provided.

Jairo Llopis and others added 23 commits November 18, 2023 00:55
Really I'm just renaming partner_contact_base.
The new name is more self-explanatory.
…#315)

[MIG] Migration partner_contact_birthdate partner_contact_gender partner_contact_personal_information_page to v10
- fax field removed from res.partner
- 2to3 on all py files
- add contributor and update README
- use hasclass in place of @Class in xpath expr
- improve tests

[FIX] typo and clean README
@Daemo00 Daemo00 mentioned this pull request Nov 18, 2023
63 tasks
@Daemo00 Daemo00 marked this pull request as ready for review November 18, 2023 00:14
@pedrobaeza pedrobaeza changed the title [MIG] partner_contact_personal_information_page [17.0][MIG] partner_contact_personal_information_page: Migration to version 17.0 Nov 18, 2023
@pedrobaeza
Copy link
Member

/ocabot migration partner_contact_personal_information_page

@OCA-git-bot OCA-git-bot added this to the 17.0 milestone Nov 18, 2023
Copy link
Contributor

@FernandoRomera FernandoRomera left a comment

Choose a reason for hiding this comment

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

Test in runboat, Ok.

Copy link

@AntoniRomera AntoniRomera left a comment

Choose a reason for hiding this comment

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

LGTM
Code Review OK

@OCA-git-bot
Copy link
Contributor

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

@pedrobaeza
Copy link
Member

Please put the pre-commit auto fixes commit (before the migration one), and you can put it as maintainer in the same commit as the migration.

@Daemo00 Daemo00 force-pushed the 17.0-mig-partner_contact_personal_information_page branch from 7d60e48 to a9302a6 Compare December 3, 2023 10:48
@Daemo00
Copy link
Contributor Author

Daemo00 commented Dec 3, 2023

Thanks everyone for having a look!

Please put the pre-commit auto fixes commit (before the migration one), and you can put it as maintainer in the same commit as the migration.

There is already a commit (2e732bc) dedicated to pre-commit auto fixes before the migration commit, but maybe I have misunderstood what you are suggesting.
I have squashed the migration and adoption commits.

Let me know if anything else is needed.

Copy link
Member

@etobella etobella left a comment

Choose a reason for hiding this comment

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

/ocabot merge nobump

@OCA-git-bot
Copy link
Contributor

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

@OCA-git-bot OCA-git-bot merged commit 9f32934 into OCA:17.0 Dec 3, 2023
5 checks passed
@OCA-git-bot
Copy link
Contributor

Congratulations, your PR was merged at 442a17a. 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.