[19.0][MIG] maintenance_equipment_hierarchy

[robyf70]

Migrated to v19.0

[BhaveshHeliconia]

Code review LGTM!

[BhaveshHeliconia]

@robyf70 could you please squash the administrative and bot commits?

[OCA-git-bot]

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). 🤖

[robyf70]

@robyf70 could you please squash the administrative and bot commits?

@BhaveshHeliconia Sure, but how I can do that?

[dalonsod]

@robyf70 please check https://github.com/OCA/maintainer-tools/wiki/Merge-commits-in-pull-requests#mergesquash-the-commits-generated-by-bots-or-weblate

[robyf70]

@robyf70 please check https://github.com/OCA/maintainer-tools/wiki/Merge-commits-in-pull-requests#mergesquash-the-commits-generated-by-bots-or-weblate

Thanks @dalonsod

[dalonsod]

@robyf70 review new commit history, it seems that you've make more squashs than required. The goal is only quash those administrative (bot/weblate) commits that were generated by the same action, usually close together. But if you see at generated history, even some migration commits (like 18.0, 17.0, 15.0, or 14.0) are lost.

[BhaveshHeliconia]

@robyf70 I’m suggesting one approach that should help keep the migration history clean. If you have another way to achieve the same result, that’s fine too. Otherwise, you can follow this approach:

Remove the existing commits locally without pushing them, rerun the migration process to generate the proper commit history, and then cherry-pick your migration commit from this PR.

After that, squash the administrative and bot/weblate commits as per the guidance and push again.