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][16.0] product_special_type (from v10.0) #1383

Closed
wants to merge 17 commits into from
Closed

[MIG][16.0] product_special_type (from v10.0) #1383

wants to merge 17 commits into from

Conversation

acsonefho
Copy link
Contributor

Migration of module product_special_type.

No special change, only pre-commit stuff.

nbessi and others added 13 commits July 12, 2023 11:24
@acsonefho
Copy link
Contributor Author

@rousseldenis Can review this please? 🙏

@acsonefho acsonefho mentioned this pull request Jul 12, 2023
Closed
@acsonefho acsonefho changed the title [MIG] product_special_type (from v10.0) [MIG][16.0] product_special_type (from v10.0) Jul 12, 2023
rousseldenis
rousseldenis reviewed Jul 20, 2023
View reviewed changes
product_special_type/__manifest__.py
'summary':
'''
"name": "Product Special Types",
"version": "16.0.1.0.0",
Copy link
Contributor

Choose a reason for hiding this comment

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

@acsonefho Could you follow migration guide ? https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-16.0#technical-method-to-migrate-a-module-from-150-to-160-branch

Version change should appear in a migration commit and not in pre-commit stuff. Thanks

@rousseldenis
Copy link
Contributor

/ocabot migration product_special_type

@OCA-git-bot OCA-git-bot added this to the 16.0 milestone Jul 20, 2023
@OCA-git-bot OCA-git-bot mentioned this pull request Jul 17, 2023
Open
60 tasks
@rousseldenis
Copy link
Contributor

@acsonefho

@FrancoMaxime FrancoMaxime force-pushed the 16.0-mig-product_special_type branch 2 times, most recently from cffc882 to 7bdd3bf Compare September 13, 2023 09:47
@FrancoMaxime
Copy link
Member

Hi @rousseldenis, I fixed your comment, can you review again?

@FrancoMaxime FrancoMaxime force-pushed the 16.0-mig-product_special_type branch from 7bdd3bf to feacbee Compare September 13, 2023 10:48
@acsonefho
Copy link
Contributor Author

@rousseldenis Can you merge this one please?

@github-actions 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 Feb 18, 2024
@acsonefho
Copy link
Contributor Author

@rousseldenis Can you use your super-power please?

@github-actions github-actions bot removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Feb 25, 2024
@github-actions 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 Jun 30, 2024
@acsonefho acsonefho requested a review from rousseldenis July 1, 2024 05:05
@github-actions github-actions bot removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jul 7, 2024
@github-actions 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 Nov 10, 2024
@github-actions github-actions bot closed this Dec 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@rousseldenis rousseldenis Awaiting requested review from rousseldenis

Assignees
No one assigned
Labels
migration 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.
10 participants
@acsonefho @rousseldenis @FrancoMaxime @OCA-git-bot @nbessi @guewen @eLBati @pedrobaeza @sbidoul @oca-travis