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

[12.0][base_partner_sequence] fix unique ref on write #686

Merged
merged 1 commit into from May 8, 2019

Conversation

sbejaoui
Copy link
Contributor

@sbejaoui sbejaoui commented Jan 9, 2019

@sbejaoui sbejaoui changed the title [12.0][base_partner_sequence] fix unique ref on write [12.0][WIP][base_partner_sequence] fix unique ref on write Jan 9, 2019
@pedrobaeza
Copy link
Member

If you are notifying an issue at the same time you fix it with a PR, better to simply put the issue text in the PR.

@pedrobaeza pedrobaeza added this to the 12.0 milestone Jan 9, 2019
@sbejaoui sbejaoui force-pushed the 12.0-fix_unique_ref_on_write branch from ddfbc58 to 8482138 Compare January 9, 2019 10:35
@sbejaoui sbejaoui force-pushed the 12.0-fix_unique_ref_on_write branch from 8482138 to e59555f Compare January 9, 2019 10:37
@sbejaoui sbejaoui changed the title [12.0][WIP][base_partner_sequence] fix unique ref on write [12.0][base_partner_sequence] fix unique ref on write Jan 9, 2019
@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). 🤖

@pedrobaeza pedrobaeza merged commit f7aad66 into OCA:12.0 May 8, 2019
@sbejaoui sbejaoui deleted the 12.0-fix_unique_ref_on_write branch July 23, 2019 09:46
chienandalu pushed a commit to Tecnativa/partner-contact that referenced this pull request Nov 28, 2019
[12.0][base_partner_sequence] fix unique ref on write
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.

None yet

4 participants