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

[15.0][FIX] upgrade_analysis: new modules cannot be merged/renamed in same version #3142

Open
wants to merge 2 commits into
base: 15.0
Choose a base branch
from

Conversation

MiquelRForgeFlow
Copy link
Contributor

Explanation of first commit: v14 has OCA's 10n_eu_oss (https://github.com/OCA/account-fiscal-rule/tree/14.0/l10n_eu_oss), which is renamed in v15 to l10n_eu_oss_oca (https://github.com/OCA/account-fiscal-rule/tree/15.0/l10n_eu_oss_oca) due to new module Odoo's 10n_eu_oss (https://github.com/odoo/odoo/tree/15.0/addons/l10n_eu_oss). Thus, it doesn't makes sense to have in the coverage file the row |[new] 10n_eu_oss | |Renamed to l10n_eu_oss_oca|.

Second commit it's obvious, we don't want OU modules appearing in the coverage file.

@OCA-git-bot
Copy link
Contributor

Hi @StefanRijnhart, @legalsylvain,
some modules you are maintaining are being modified, check this out!

@StefanRijnhart
Copy link
Member

Thanks for putting the detailed explanation in the PR but can you put in in the commit message as well, and maybe a comment or extra clarification in the docstring?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants