Skip to content

[FW][IMP] academic: add company in same partner dni #240

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

Merged
merged 1 commit into from
Mar 25, 2025

Conversation

fw-bot-adhoc
Copy link
Contributor

Forward-Port-Of: #231

@roboadhoc
Copy link

@fw-bot-adhoc
Copy link
Contributor Author

@lef-adhoc @matiasperalta1 cherrypicking of pull request #231 failed.

stdout:

Auto-merging academic/views/res_partner_views.xml
Auto-merging academic/models/res_partner.py
CONFLICT (content): Merge conflict in academic/models/res_partner.py
Auto-merging academic/i18n/es_UY.po
CONFLICT (content): Merge conflict in academic/i18n/es_UY.po
Auto-merging academic/i18n/es.po
Auto-merging academic/__manifest__.py
CONFLICT (content): Merge conflict in academic/__manifest__.py

stderr:

13:44:15.665324 git.c:444               trace: built-in: git cherry-pick bb23121395b997b718abd26c8591dbb8dd870d81
error: could not apply bb23121... [IMP] academic: add company in same partner dni
hint: after resolving the conflicts, mark the corrected paths
hint: with 'git add <paths>' or 'git rm <paths>'
hint: and commit the result with 'git commit'
----------
status:

Either perform the forward-port manually (and push to this branch, proceeding as usual) or close this PR (maybe?).

In the former case, you may want to edit this PR message as well.

More info at https://github.com/odoo/odoo/wiki/Mergebot#forward-port

@lef-adhoc lef-adhoc force-pushed the 18.0-17.0-t-49721-lef-zz4I-fw branch from 7e3d27f to 01e2229 Compare March 21, 2025 16:39
@jjscarafia jjscarafia merged commit 1745a3d into ingadhoc:18.0 Mar 25, 2025
2 of 3 checks passed
@jjscarafia jjscarafia deleted the 18.0-17.0-t-49721-lef-zz4I-fw branch March 25, 2025 19:40
@jjscarafia
Copy link
Member

los errores de runbot eran por otros cambios

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.

4 participants