Skip to content

[19.0][MIG] project_tag_hierarchy: Migration to 19.0#1713

Open
stferraro wants to merge 12 commits intoOCA:19.0from
Jenrax-git:19.0-mig-project_tag_hierarchy
Open

[19.0][MIG] project_tag_hierarchy: Migration to 19.0#1713
stferraro wants to merge 12 commits intoOCA:19.0from
Jenrax-git:19.0-mig-project_tag_hierarchy

Conversation

@stferraro
Copy link
Copy Markdown

No description provided.

@OCA-git-bot OCA-git-bot added series:19.0 mod:project_tag_hierarchy Module project_tag_hierarchy labels Apr 25, 2026
@stferraro stferraro mentioned this pull request Apr 25, 2026
42 tasks
Copy link
Copy Markdown

@WesleyOliveira98 WesleyOliveira98 left a comment

Choose a reason for hiding this comment

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

@stferraro stferraro force-pushed the 19.0-mig-project_tag_hierarchy branch 2 times, most recently from dfc47c7 to 51d07a7 Compare April 26, 2026 02:58
Copy link
Copy Markdown

@WesleyOliveira98 WesleyOliveira98 left a comment

Choose a reason for hiding this comment

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

The PR title stll not following the OCA patterns, should be:
[19.0][MIG] <module>: Migration to 19.0

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-19.0#how-to
Image

@stferraro stferraro force-pushed the 19.0-mig-project_tag_hierarchy branch from 51d07a7 to f2a361d Compare April 28, 2026 01:04
Copy link
Copy Markdown

@WesleyOliveira98 WesleyOliveira98 left a comment

Choose a reason for hiding this comment

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

@stferraro you need to change the PR title to [19.0][MIG] <module>: Migration to 19.0, the commit title was correct, should be [MIG] <module>: Migration to 19.0
Image

Everything else is ok, just change this

@stferraro stferraro force-pushed the 19.0-mig-project_tag_hierarchy branch from f2a361d to f9c0671 Compare April 28, 2026 12:44
Copy link
Copy Markdown

@WesleyOliveira98 WesleyOliveira98 left a comment

Choose a reason for hiding this comment

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

  • In your PR, click on this button:
Image
  • Insert the title: [19.0][MIG] project_tag_hierarchy: Migration to 19.0

  • Click on save

Image
  • Then, change the commit message: [MIG] project_tag_hierarchy: Migration to 19.0

@stferraro stferraro changed the title 19.0 mig project tag hierarchy [19.0][MIG] project_tag_hierarchy: Migration to 19.0 Apr 28, 2026
Copy link
Copy Markdown
Member

@CristianoMafraJunior CristianoMafraJunior left a comment

Choose a reason for hiding this comment

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

LGTM

@stferraro stferraro force-pushed the 19.0-mig-project_tag_hierarchy branch from f9c0671 to f3c1e5c Compare April 28, 2026 19:05
Comment thread project_tag_hierarchy/__manifest__.py Outdated
# License AGPL-3.0 or later (https://www.gnu.org/licenses/agpl).
{
"name": "Project Tag Hierarchy",
"version": "19.0.1.0.1",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

19.0.1.0.0

@CristianoMafraJunior
Copy link
Copy Markdown
Member

squash 2 commits

@stferraro stferraro force-pushed the 19.0-mig-project_tag_hierarchy branch from 673f244 to 685a4eb Compare April 29, 2026 00:02
Copy link
Copy Markdown

@WesleyOliveira98 WesleyOliveira98 left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Copy Markdown

@luisDIXMIT luisDIXMIT left a comment

Choose a reason for hiding this comment

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

Code review and tested on runboat, LGTM!

@stferraro
Copy link
Copy Markdown
Author

Hi, @CristianoMafraJunior please reviews this pr and approved

@OCA-git-bot
Copy link
Copy Markdown
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). 🤖

Copy link
Copy Markdown

@Yusuke1998 Yusuke1998 left a comment

Choose a reason for hiding this comment

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

LGTM!

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.

10 participants