-
-
Notifications
You must be signed in to change notification settings - Fork 856
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
[11.0] mig partner contact in several companies #507
[11.0] mig partner contact in several companies #507
Conversation
I think a need to squash :) But don't know how ? |
@pedrobaeza @gurneyalex don't understand runbot and codecov red bullet ... some help ? |
The problem with the runbot is that your code raises a WARNING: |
Ok will change this :) thanks @etobella |
02f48bd
to
0e5b0e3
Compare
|
@pedrobaeza all green :) ready for review ? |
Well, I'm not directly interested in this module, so let's wait for other interested reviewers. Any way, I think if you rebase over current branch, you will get coverage, which is a good indicator also. |
@pedrobaeza ok no probleme will rebase. thanks |
0e5b0e3
to
345ccfa
Compare
@yajo @pedrobaeza what should I do to pass codecov ? it is just 10.0 to 11.0 migration no improvement or new function ... |
In this case codecov indicates that some merged code is not being tested. If you hit "Details > Diff", you'll see some red lines indicating that. You'd have to add some test for those lines to go over the target patch coverage (96.34%) and to avoid lowering the current project coverage ratio. It would be a much appreciated effort, although I wouldn't require such thing IMHO. |
49f3034
to
1b8a746
Compare
@yajo done ;) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool! Please squash all migration-related commits into one for the final merge 😊
92e79d1
to
43e65d6
Compare
@yajo like that ? |
With 867d552 too |
@yajo : did not understand why this commit is shown, in my branch all commit are squashed in one. |
@njeudy don't worry, let me show you. Look at the commits in the PR: I highlighted all of the remaining translation commits. The normal flow would be:
That should open the editor you have configured and show all the list of commits from your branch. They should appear in this fashion:
Now you should cut all those lines that I marked in red and move them to the bottom, just before your migration commit, and mark as
Then save and exit. Git will start picking all code commits, then it will pick 1st translation commit and fixup (squash discarding commit message) all of other translation commits in that one, then it will pick your migration commit and will let a clean branch! There's chance that merge conflicts appear, in such case install
If you even use that fixup system to remove the duplicate commits from your branch, that would be even more awesome, but this should be just fine with that. |
372788d
to
6ae7320
Compare
@yajo thanks for your help, now it should be ok and have learn a lot if git rebase tricks :) |
- Remove Domain Error on contact view. - Additionally, improve behaviour of personal contact info page. - Change to README. - No longer dependent on partner_contact_personal_information_page - Added tests for ir_actions - Include extra demo data. - Increase test coverage. - Remove birthdate from demo data.
…ersonal_contact_information'
* [MIG] inital work to 10.0 * [FIX] restore computed field - select=1 is not usable anymore ... * [FIX] convert _fields_sync to new api * [FIX] restore form . import statement * [FIX] readme with last template. * [FIX] import statement. * [FIX] check all tests * [FIX] Flake8 errors fixes * [FIX] flake 8 * [FIX] wrong obj call self -> self.contact_id * [FIX] typo * [FIX] flake 8 * [FIX] add index on contact_type * [fix] use in statement on test * [FIX] update base action with new context * [FIX] test fixes * [FIX] test work * [FIX] flake 8 over indent * [FIX] fixes on lastest comments - better readability - remove <data></data> tags * [FIX] model that same pattern for _fields_sync - add test ensure_once() * [FIX] remove last data xml tags * [FIX] fix action test * [FIX] typo in import statement * [FIX] remove logger from tests * [FIX] new flake8 compute method name for OCA * [FIX] minor typo * [FIX] partner_contact_in_several_companies: remove contributor key in manifest * [FIX] partner_contact_in_several_companies: residual onchange on partner view * Revert "[FIX] partner_contact_in_several_companies: remove contributor key in manifest" This reverts commit 56e511a. * [FIX] partner_contact_personal_information_page: clean manifest and authors * [FIX] partner_contact_in_several_companies: required = True not needed
Really I'm just renaming partner_contact_base. The new name is more self-explanatory.
OCA#315) [MIG] Migration partner_contact_birthdate partner_contact_gender partner_contact_personal_information_page to v10
- fax field removed from res.partner - 2to3 on all py files - add contributor and update README - use hasclass in place of @Class in xpath expr - improve tests [FIX] typo and clean README
5c2bb83
to
0362443
Compare
@simahawk Ok done squash commit from same user in one |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I'd squash commits like "make module uninstallable" and alike, just because they are useless in this context. But is not a blocker and we don't have guidelines for this ;)
@pedrobaeza @simahawk @yajo Ok to merge ? |
This has broken Travis. I have already fixed one issue, but it seems that there are more. This can't be installed. Please check https://travis-ci.org/OCA/partner-contact/jobs/317716741#L780 |
Please fix Travis after merging this. |
Solved thanks to @drdran |
In the same PR because dependency