[IMP] Add support for module renaming #74
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Different approach than #64 to move/rename a module to address issue #11:
oca-port {source} {target} {addon_path} [--move-to {new_addon_path}]
git-filter-repo
, thanks for the tip @trisdoan )usegit filter-branch
to rename the module (see [18.0][MIG] commission + rename to commission_oca commission#610 (comment))PortAddonPullRequest
to work on moved/renamed module (rework patches to apply to target the new module/folder name, ...)Optional (can be done in a future PR):
.oca/oca-port/
directory withStorage
class.oca/oca-port/
so a migration attempt will automatically detect that this module has been renamed in target branch, launching analysis with the right module nameExample
Migrate & rename a module at the same time:
Module already migrated under a different name: ```sh $ oca-port origin/17.0 origin/18.0 stock_packaging_calculator ℹ️ stock_packaging_calculator has been renamed product_packaging_calculator in origin/18.0 product_packaging_calculator already exists on origin/18.0, checking PRs to port... ```