Skip to content

Conversation

@BhaveshHeliconia
Copy link
Contributor

No description provided.

@LoisRForgeFlow
Copy link
Contributor

Hi @HeliconiaSolutions could you cherry-pick this patch #90 here?

@BhaveshHeliconia
Copy link
Contributor Author

@LoisRForgeFlow , please review.it's done.

@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 29, 2025
@LoisRForgeFlow LoisRForgeFlow removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jun 30, 2025
Copy link
Contributor

@LoisRForgeFlow LoisRForgeFlow left a comment

Choose a reason for hiding this comment

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

@BhaveshHeliconia Sorry for the slow review here.

Comparing v17 commit history with this PR, I still miss one more commit: 7e4ed99

Coud you add it?

@BhaveshHeliconia
Copy link
Contributor Author

@LoisRForgeFlow, Please Review.

Copy link
Contributor

@LoisRForgeFlow LoisRForgeFlow left a comment

Choose a reason for hiding this comment

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

@BhaveshHeliconia Thanks! I still see on issue in the history

image

Could you fix the commit message of this commit to be "[MIG] repair_stock: Migration to 18.0"

DavidJForgeFlow and others added 10 commits August 7, 2025 10:17
`repair_id` is reserved to the stock.moves directly related
to the execution of the repair order and has associated logic
in odoo core code (like assigning the picking type)
To avoid unexpected behaviors, we use `related_repair_id` to
signal auxiliar stock moves that are not directly related to
repair execution.

To not break existing modules depending on it, support for
`repair_id` is kept but it is recommended to remove in v18.
@BhaveshHeliconia
Copy link
Contributor Author

@LoisRForgeFlow : It's done now. Thanks, and sorry for the delay.

@LoisRForgeFlow
Copy link
Contributor

/ocabot migration repair_stock

@OCA-git-bot OCA-git-bot added this to the 18.0 milestone Aug 7, 2025
@LoisRForgeFlow
Copy link
Contributor

@BhaveshHeliconia I still miss commits from v17 history, like this one 7e4ed99

This module has been migrated over several versions and has good tests coverage.
@BhaveshHeliconia
Copy link
Contributor Author

@LoisRForgeFlow : I've added it—thanks for pointing it out. Please check.

Copy link
Contributor

@LoisRForgeFlow LoisRForgeFlow left a comment

Choose a reason for hiding this comment

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

LGTM 👍

@LoisRForgeFlow
Copy link
Contributor

/ocabot merge nobump

@OCA-git-bot
Copy link
Contributor

What a great day to merge this nice PR. Let's do it!
Prepared branch 18.0-ocabot-merge-pr-77-by-LoisRForgeFlow-bump-nobump, awaiting test results.

@OCA-git-bot OCA-git-bot merged commit 3a9a332 into OCA:18.0 Aug 20, 2025
7 checks passed
@OCA-git-bot
Copy link
Contributor

Congratulations, your PR was merged at 69e33e8. Thanks a lot for contributing to OCA. ❤️

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.

6 participants