[REM] l10n_it_riba: It is already named l10n_it_riba_oca#5627
Conversation
|
Please respect commit name guide-line, like [18.0][OU-FIX] etc |
|
Thanks for having a look!
There is no specific guideline for this project's commit name, see https://github.com/OCA/OpenUpgrade/blob/18.0/CONTRIBUTING.md#project-specific-guidelines:
but looks like everyone is creating their own instead 🤔 So I followed the usual guidelines in https://github.com/OCA/odoo-community.org/blob/master/website/Contribution/CONTRIBUTING.rst; I changed the commit message anyway because |
This is probably a not written recent guideline, see #5098 (comment) |
There was a problem hiding this comment.
Thanks for your PR @SirPyTech
You are right there is no guideline for commit as there are divergent view whether OU- should be added between brackets or not.
From my pov, this should be a FIX rather than a IMP and should not mention openupgrade_scripts but apriori instead.
Also it is useful for reviewers if you can add version number in PR name, [18.0]...
|
This PR has the |
|
This rename in 16 then seems incorrect: https://github.com/OCA/OpenUpgrade/blob/16.0/openupgrade_scripts/apriori.py#L66 Isn't it? |
Thanks for having a look! Let me summarize the situation first:
So the rename you linked for "l10n_it_ricevute_bancarie": "l10n_it_riba_oca",is actually correct. And remember that all this mess is because Odoo added an enterprise module named |
Thanks for having a look!
I don't really like repeating the version information in multiple places, because we already have that same information in the base branch and now also in a dedicated label; I feel like adding it in the PR title is redundant. |
|
OK, let's continue and let the commit message aside. |
Thanks! 🙏 |


The rename has been merged a few days ago: OCA/l10n-italy#4856.