Skip to content

Conversation

@DucTruongKomit
Copy link

Module migrated to version 19.0

@DucTruongKomit DucTruongKomit force-pushed the 19.0-mig-account_usability branch from d3e5b79 to da360f3 Compare November 24, 2025 08:41
@quoc-pn
Copy link
Member

quoc-pn commented Dec 10, 2025

@DucTruongKomit Why there is only 1 commit in your PR? Please help check again.

BTW, there is a PR #2174

@DucTruongKomit
Copy link
Author

@DucTruongKomit Why there is only 1 commit in your PR? Please help check again.

BTW, there is a PR #2174

Base on the ID, I created the PR before that PR. That PR is duplicated. The PR must be only 1 commit.

@quoc-pn
Copy link
Member

quoc-pn commented Dec 10, 2025

The PR must be only 1 commit.

@DucTruongKomit, did you follow the OCA migration intruction?

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

@DucTruongKomit
Copy link
Author

The PR must be only 1 commit.

@DucTruongKomit, did you follow the OCA migration intruction?

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

yes, i did try to follow, If there is any point I miss, could you share with me? Thank in adavance.

@quoc-pn
Copy link
Member

quoc-pn commented Dec 10, 2025

@DucTruongKomit

I think you miss the section "Technical method to migrate a module ..."

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-19.0#technical-method-to-migrate-a-module-from-180-to-190-branch

@RyanTranAVB
Copy link

I didn't notice this one since it ins't mentioned in #2155. Please do that the next time.

Hence, this looks wrong since there is only 1 commit which should not be the case

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants