Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[MIG] sale_order_carrier_auto_assign: Migration to 16.0 #2533

Merged

Conversation

matiasperalta1
Copy link
Contributor

No description provided.

@matiasperalta1 matiasperalta1 force-pushed the 16.0-mig-sale_order_carrier_auto_assign branch from 4936ef2 to 1f319e2 Compare May 30, 2023 13:58
Copy link

@florenciafrigieri2 florenciafrigieri2 left a comment

Choose a reason for hiding this comment

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

Functional review ok

@OCA-git-bot
Copy link
Contributor

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

@rousseldenis
Copy link
Sponsor Contributor

/ocabot migration sale_order_carrier_auto_assign

@OCA-git-bot OCA-git-bot added this to the 16.0 milestone Jun 14, 2023
@OCA-git-bot OCA-git-bot mentioned this pull request Jun 14, 2023
97 tasks
_inherit = "sale.order"

def action_confirm(self):
if config["test_enable"] and not self.env.context.get(
Copy link
Sponsor Contributor

Choose a reason for hiding this comment

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

@matiasperalta1 @grindtildeath I don't like such code. Better to add a setting to enable the behaviour that breaks standard one. But not blocking

Copy link
Sponsor Contributor

Choose a reason for hiding this comment

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

@matiasperalta1 Could you put at least in ROADMAP we need to add a configuration setting ?

Copy link
Contributor

Choose a reason for hiding this comment

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

@rousseldenis I mplemented that in another PR:
#2837

Choose a reason for hiding this comment

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

Why adding this in an other PR ? Would you not prefer to include it here ?

Copy link
Contributor

Choose a reason for hiding this comment

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

I would prefer. But probably @matiasperalta1 did not had opportunity to implement that.

@dreispt
Copy link
Sponsor Member

dreispt commented Jan 27, 2024

/ocabot merge nobump

@OCA-git-bot
Copy link
Contributor

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

OCA-git-bot added a commit that referenced this pull request Jan 27, 2024
Signed-off-by dreispt
@OCA-git-bot
Copy link
Contributor

It looks like something changed on 16.0 in the meantime.
Let me try again (no action is required from you).
Prepared branch 16.0-ocabot-merge-pr-2533-by-dreispt-bump-nobump, awaiting test results.

@OCA-git-bot OCA-git-bot merged commit 00e780c into OCA:16.0 Jan 27, 2024
@OCA-git-bot
Copy link
Contributor

Congratulations, your PR was merged at 1342462. 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.