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] base_user_role: Migration to 13.0 #46

Merged
merged 30 commits into from
Jan 30, 2020

Conversation

sebalix
Copy link
Contributor

@sebalix sebalix commented Oct 1, 2019

No description provided.

@oca-clabot
Copy link

Hey @sebalix, thank you for your Pull Request.

It looks like some users haven't signed our Contributor License Agreement, yet.
You can read and sign our full Contributor License Agreement here: http://odoo-community.org/page/cla
Here is a list of the users:

Appreciation of efforts,
OCA CLAbot

@sebalix sebalix mentioned this pull request Oct 1, 2019
8 tasks
@jcdrubay
Copy link

jcdrubay commented Oct 2, 2019

Hi this is the gihub login of duc.dd@komit-consulting.com: https://github.com/novawish

The email address ducdd@komit-consulting.com is a typo.

Copy link

@jcdrubay jcdrubay left a comment

Choose a reason for hiding this comment

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

Thank you @sebalix :) I have added 2 small comments. The rest LGTM.

<odoo>

<record model="ir.module.category" id="ir_module_category_role">
<field name='name'>User roles</field>
Copy link

Choose a reason for hiding this comment

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

I don' think this is used anywhere, and I think that we should NOT create this module category as it seems like other similar modules in Odoo core are using the category Tools or Extra Tools.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This module category aims to be linked to role/group you create in your own custom module (https://github.com/odoo/odoo/blob/13.0/odoo/addons/base/models/res_users.py#L101) if you want. By doing this you'll have the section 'User roles' in the "Access rights" tab on the user form which will regroup all groups related to role. Without it, all these groups will be in the 'Other' section.
I could add a comment above this XML record about that.

Comment on lines 1 to 7
[ This file must be present and contains the usage instructions
for end-users. As all other rst files included in the README,
it MUST NOT contain reStructuredText sections
only body text (paragraphs, lists, tables, etc). Should you need
a more elaborate structure to explain the addon, please create a
Sphinx documentation (which may include this file as a "quick start"
section). ]
Copy link

Choose a reason for hiding this comment

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

I guess you should remove this lines

@pedrobaeza pedrobaeza added this to the 13.0 milestone Oct 2, 2019
@bealdav
Copy link
Member

bealdav commented Oct 4, 2019

Hi @sebalix is it possible to add these commits in this PR ?

https://github.com/OCA/server-tools/pull/1489/commits

Not blocking for me but you know perfectly this module, it could be nice

Thanks in advance

@sebalix sebalix force-pushed the 13.0-mig-base_user_role branch 2 times, most recently from ba3ae7e to 48da5cd Compare October 4, 2019 14:53
@bealdav
Copy link
Member

bealdav commented Oct 4, 2019

Thanks @sebalix

@sebalix
Copy link
Contributor Author

sebalix commented Oct 5, 2019

@bealdav I'll continue to work on this the next week. There are a lot of fix and improvements in different branches, all of them need to be consolidated. It should be ok for 13.0 now (I just need to rebase some of them).
BTW I would like a tool/git command to compare commits between different branches based not on the commit hash (which has changed) but on other keys like author/date/message to know what to forward port/backport on a branch.

Copy link
Contributor

@alan196 alan196 left a comment

Choose a reason for hiding this comment

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

Tested locally 👍 works as expected

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

@lmgr0312
Copy link

LGTM

@pedrobaeza
Copy link
Member

/ocabot merge

@OCA-git-bot
Copy link
Contributor

What a great day to merge this nice PR. Let's do it!
Prepared branch 13.0-ocabot-merge-pr-46-by-pedrobaeza-bump-no, awaiting test results.

OCA-git-bot added a commit that referenced this pull request Nov 21, 2019
Signed-off-by pedrobaeza
@OCA-git-bot
Copy link
Contributor

@pedrobaeza your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-46-by-pedrobaeza-bump-no.

After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red.

@pedrobaeza
Copy link
Member

You have to rebase and pass black in pre-commit. See https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-13.0

Laurent-Corron pushed a commit to acsone/server-backend that referenced this pull request Nov 26, 2019
original branch from OCA#46
@eggu68
Copy link

eggu68 commented Dec 16, 2019

@sebalix @pedrobaeza @Laurent-Corron what is the status of this migration? I see it did not pass all checks? Thank you for your good work.

@sebalix
Copy link
Contributor Author

sebalix commented Dec 16, 2019

@pedrobaeza @eggu68 thank you to notice me about this. It's done, all checks are green now. Ready to be merged.

@eggu68
Copy link

eggu68 commented Jan 27, 2020

@pedrobaeza can this be merged to 13.0 now? Thank you.

@pedrobaeza
Copy link
Member

/ocabot merge

@sebalix
Copy link
Contributor Author

sebalix commented Jan 30, 2020

@pedrobaeza sorry for the delay, it's now rebased + isort.cfg updated to resolve the upcoming conflict. Ready to be merged.

@pedrobaeza
Copy link
Member

/ocabot merge

@OCA-git-bot
Copy link
Contributor

This PR looks fantastic, let's merge it!
Prepared branch 13.0-ocabot-merge-pr-46-by-pedrobaeza-bump-no, awaiting test results.

OCA-git-bot added a commit that referenced this pull request Jan 30, 2020
Signed-off-by pedrobaeza
@OCA-git-bot OCA-git-bot merged commit 7615a99 into OCA:13.0 Jan 30, 2020
@OCA-git-bot
Copy link
Contributor

Congratulations, your PR was merged at c7dc687. Thanks a lot for contributing to OCA. ❤️

@sebalix sebalix deleted the 13.0-mig-base_user_role branch January 30, 2020 09:12
SiesslPhillip pushed a commit to grueneerde/OCA-server-backend that referenced this pull request Nov 20, 2024
Syncing from upstream OCA/server-backend (13.0)
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.