Closed chaule97 closed 4 weeks ago
@chaule97 Thanks for this. Don't forget to add the depending PR in this one description to help review
Sorry @TDu you are not allowed to mark the addon tobe migrated.
To do so you must either have push permissions on the repository, or be a declared maintainer of all modified addons.
If you wish to adopt an addon and become it's maintainer, open a pull request to add your GitHub login to the maintainers
key of its manifest.
Salut @rousseldenis , I have rebase. Could you merge again?
Salut @rousseldenis , I have rebase. Could you merge again?
migration
command is not a merge. Just to update Migration PR :sweat_smile:
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). 🤖
/ocabot merge nobump
On my way to merge this fine PR! Prepared branch 18.0-ocabot-merge-pr-1859-by-simahawk-bump-nobump, awaiting test results.
Congratulations, your PR was merged at 644ddcbc89d06513ed32c2fd36fc4069adcaf810. Thanks a lot for contributing to OCA. ❤️
/caobot migration partner_identification_unique_by_category