Pedro M. Baeza

@usmanfarzandali you don't need to register in any place (apart from signing the CLA - https://odoo-community.org/about/cla). Just make the pull request following the standard GitHub contributions, forking the repo, and...

This one should be handled by one of the PSCs, as the given errors are out of scope of the systematic fixes I'm doing.

Isn't better to adapt templates to a "safe" syntax?

@yajo as you know both pieces. Are there too many changes to do?

Being in the migration list won't speed up its migration. If you have a PR migrating it, then from the PR a command can be launched to include it here.

The module is too simple to be split IMO. If you want compatibility with `account_invoice_merge`, put the needed hooks in the base one, and develop `account_invoice_merge_grouping_criteria` o similar.

OK, I'm not using anymore 12.0, although it seems a bit weird, as pre-v13 resets the values of each compute to the default one, but it doesn't hurt: /ocabot merge...

Merging blindly due to the reviews: /ocabot merge nobump

It can't be merged without removing the unreleased dependency

> Module `account_move_force_removal` seems not necessary anymore for V16. The module was basically just bypassing the check made in method `_unlink_forbid_parts_of_chain()` that was ensuring that the sequence number was the...