Pedro M. Baeza
Pedro M. Baeza
This is not correct. The file goes inside a module folder, not on the root, and it's populated automatically by pre-commit when needed.
I don't get the goal of this, because it's perfectly fine working with the previous approach. Anyway, I don't use pip for Odoo and I don't like it.
Yeah, the umpteenth Python package manager... The question is that Odoo modules are not Python packages, and trying to make them to "appear" as if they are, only adds layers...
A Doodba copier template is easiest in my opinion and covering more cases (devel, prod and demo instances, Mailhog, debuggers...)
Yes, it's incompatible by some reasons.
The reasons are technical, and they can be in any moment bypassed/fixed. Don't think it's another kind of resistance. It's just that I don't remember right now which ones.
/ocabot merge nobump
@AndreuOForgeFlow three warnings of this module has appeared on the CI, turning it red: https://github.com/OCA/contract/actions/runs/16004911263/job/45149095295#step:8:463 Can you please fix them?
/ocabot migration account_payment_credit_card I don't think we should restrict them, as there can be legit debits in these journals. The README is clear stating about vendor bills, so nothing more...
/ocabot merge nobump