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.

Sign up for GitHub

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

Jump to bottom

[MIG] partner_identification: Migration to 16.0 #1374

Closed
wants to merge 2 commits into from
Closed

[MIG] partner_identification: Migration to 16.0 #1374

wants to merge 2 commits into from

Conversation

deu-dev
Copy link

@deu-dev deu-dev commented Oct 10, 2022

AnizR
AnizR reviewed Oct 10, 2022
View reviewed changes
partner_identification/tests/test_res_partner.py Outdated
from .fake_models import ResPartner, setup_test_model, teardown_test_model


class TestResPartner(common.SavepointCase):
Copy link
Contributor

Choose a reason for hiding this comment

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

SavepointCase is deprecated. Maybe use TransactionCase?

Copy link
Author

Choose a reason for hiding this comment

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

@AnizR changed

@rousseldenis
Copy link
Contributor

/ocabot migration partner_identification

@OCA-git-bot OCA-git-bot added this to the 16.0 milestone Oct 10, 2022
@OCA-git-bot OCA-git-bot mentioned this pull request Oct 10, 2022
Open
60 tasks
@rousseldenis
Copy link
Contributor

@deu-dev Thanks for this.

Could you follow migration guide in order to keep commits history (Full process part) ? https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-16.0

@marielejeune
Copy link
Contributor

marielejeune commented Nov 9, 2022 •
edited
Loading

Hi @deu-dev, since you didn't manage to fix your PR this last month, I opened a new one here: #1397

@OCA-git-bot OCA-git-bot mentioned this pull request Nov 10, 2022
Merged
@github-actions
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 Mar 12, 2023
@github-actions github-actions bot closed this Apr 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@AnizR AnizR AnizR left review comments

Assignees
No one assigned
Labels
migration needs fixing needs review stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Milestone
16.0
Development

Successfully merging this pull request may close these issues.
5 participants
@deu-dev @rousseldenis @marielejeune @AnizR @OCA-git-bot