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] account_partner_company_group: Migration to 17.0 #1689

Closed

Conversation

pedroguirao
Copy link
Contributor

No description provided.

yankinmax and others added 13 commits March 5, 2024 11:00
Currently translated at 100.0% (3 of 3 strings)

Translation: partner-contact-16.0/partner-contact-16.0-account_partner_company_group
Translate-URL: https://translation.odoo-community.org/projects/partner-contact-16-0/partner-contact-16-0-account_partner_company_group/pt_BR/
Currently translated at 100.0% (3 of 3 strings)

Translation: partner-contact-16.0/partner-contact-16.0-account_partner_company_group
Translate-URL: https://translation.odoo-community.org/projects/partner-contact-16-0/partner-contact-16-0-account_partner_company_group/es/
Currently translated at 100.0% (3 of 3 strings)

Translation: partner-contact-16.0/partner-contact-16.0-account_partner_company_group
Translate-URL: https://translation.odoo-community.org/projects/partner-contact-16-0/partner-contact-16-0-account_partner_company_group/it/
@pedroguirao pedroguirao mentioned this pull request Mar 5, 2024
64 tasks
Copy link

@ConesaJM ConesaJM left a comment

Choose a reason for hiding this comment

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

Works OK

@MohamedOsman7
Copy link

As pedro in the other PR (#1688) said:
"Please split the changes in 2 commits according the migration guide [1], one for the automatic changes, and the other for the manual ones, and not everything in the [IMP] base_partner_company_group: pre-commit auto fixes commit.

[1] https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-17.0#technical-method-to-migrate-a-module-from-160-to-170-branch"

@CRogos
Copy link

CRogos commented Apr 18, 2024

@pedroguirao are you still working on this?

Copy link

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.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Aug 18, 2024
@github-actions github-actions bot closed this Sep 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants