pos
pos copied to clipboard
[MIG] pos_default_partner: Migration to 15.0
Hey @tupaq, thank you for your Pull Request.
It looks like some users haven't signed our Contributor License Agreement, yet. You can read and sign our full Contributor License Agreement here: http://odoo-community.org/page/cla Here is a list of the users:
- Jaime Arroyo [email protected] (no github login found)
Appreciation of efforts, OCA CLAbot
@bealdav : could you review the migration of the module you shared ? thanks !
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 15.0-ocabot-merge-pr-759-by-ivantodorovich-bump-nobump, awaiting test results.
@ivantodorovich your merge command was aborted due to failed check(s), which you can inspect on this commit of 15.0-ocabot-merge-pr-759-by-ivantodorovich-bump-nobump.
After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red.
/ocabot rebase
@ivantodorovich The rebase process failed, because command git push --force GrupoYACCK tmp-pr-759:15.0-mig-pos_default_partner
failed with output:
remote: Permission to GrupoYACCK/pos.git denied to OCA-git-bot.
fatal: unable to access 'https://github.com/GrupoYACCK/pos/': The requested URL returned error: 403
@tupaq could you rebase and fix pre-commit? That's the only thing that's blocking the PR AFAICS
Ok @ivantodorovich. rebased and fix pre-commit
I think there's some issue with your last rebase, because I see some commits for other modules that shouldn't be here.
Could you take care of it? Make sure you pull latests changes from 15.0
before rebasing
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). 🤖
CAn you review the problem? @tupaq
CAn you review the problem? @tupaq
Revised and corrected.
@etobella @ivantodorovich could you merge?
There are some merge commits here... Can you rebase and the push force?
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.