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

[MIG] base_partner_sequence: Migration to 16.0 #1371

Closed
wants to merge 1 commit into from

Conversation

deu-dev
Copy link

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

@deu-dev deu-dev force-pushed the 16.0-mig-base_partner_sequence branch from 359d093 to 4690c19 Compare October 10, 2022 12:33
Copy link
Contributor

@NL66278 NL66278 left a comment

Choose a reason for hiding this comment

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

Please follow the method that preserves commit history:

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-16.0

@marielejeune
Copy link
Contributor

Hi @deu-dev , do you plan to fix your PR? Thanks

@Nikul-OSI
Copy link
Contributor

Supersede #1453

@Nikul-OSI
Copy link
Contributor

@NL66278 @dreispt can you please close this PR?

@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 May 21, 2023
@github-actions github-actions bot closed this Jun 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs fixing 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.

4 participants