Skip to content

[FIX] export_bg: Enhance field extraction for improved export compatibility#392

Closed
fw-bot-adhoc wants to merge 1 commit intoingadhoc:19.0from
adhoc-dev:19.0-18.0-h-112744-rov-4849-fw
Closed

[FIX] export_bg: Enhance field extraction for improved export compatibility#392
fw-bot-adhoc wants to merge 1 commit intoingadhoc:19.0from
adhoc-dev:19.0-18.0-h-112744-rov-4849-fw

Conversation

@fw-bot-adhoc
Copy link
Copy Markdown
Contributor

Forward-Port-Of: #391

@roboadhoc
Copy link
Copy Markdown
Contributor

Pull request status dashboard

@fw-bot-adhoc
Copy link
Copy Markdown
Contributor Author

@rov-adhoc @maq-adhoc cherrypicking of pull request #391 failed.

stdout:

Auto-merging export_bg/models/export_bg_mixin.py
Auto-merging export_bg/static/src/views/list_controller.js
CONFLICT (content): Merge conflict in export_bg/static/src/views/list_controller.js

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

:shipit: you can use git-fw to re-do the forward-port for you locally.

⚠️ after resolving this conflict, you will need to merge it via @roboadhoc.

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

@rov-adhoc rov-adhoc force-pushed the 19.0-18.0-h-112744-rov-4849-fw branch from 798fdd1 to 019a025 Compare April 1, 2026 14:53
@rov-adhoc
Copy link
Copy Markdown
Contributor

@roboadhoc r+ npbump

@roboadhoc
Copy link
Copy Markdown
Contributor

@rov-adhoc unknown command 'npbump'.

For your own safety I've ignored everything in your entire comment.

Currently available commands:

command
help displays this help
r(eview)+ approves the PR, if it's a forwardport also approves all non-detached parents
r(eview)=<number> only approves the specified parents
r(eview)- removes approval of a previously approved PR, if the PR is staged the staging will be cancelled
retry re-tries staging a PR in the "error" state
fw=no does not forward-port this PR
fw=default forward-ports this PR normally
fw=skipci does not wait for a forward-port's statuses to succeed before creating the next one
fw=skipmerge does not wait for the source to be merged before creating forward ports
up to <branch> only ports this PR forward to the specified branch (included)
close closes this forward-port
merge integrate the PR with a simple merge commit, using the PR description as message
rebase-merge rebases the PR on top of the target branch the integrates with a merge commit, using the PR description as message
rebase-ff rebases the PR on top of the target branch, then fast-forwards
squash squashes the PR as a single commit on the target branch, using the PR description as message
delegate+ grants approval rights to the PR author
delegate=<...> grants approval rights on this PR to the specified github users
nice only stages the PR if there's room in the batch after default PRs
default stages the PR normally
priority tries to stage this PR first, then adds default PRs if the staging has room
alone stages this PR only with other PRs of the same priority
cancel=staging automatically cancels the current staging when this PR becomes ready
check fetches or refreshes PR metadata, resets mergebot state
remindme:<branch>=<message> When the PR gets forward-ported to , ping you with . can be quoted if it needs spaces.

Note: this help text is dynamic and will change with the state of the PR.

@rov-adhoc
Copy link
Copy Markdown
Contributor

@roboadhoc nobump

@rov-adhoc
Copy link
Copy Markdown
Contributor

@roboadhoc r+

@roboadhoc roboadhoc closed this in e2f657c Apr 1, 2026
@roboadhoc roboadhoc added the 18.1 label Apr 1, 2026
@roboadhoc roboadhoc deleted the 19.0-18.0-h-112744-rov-4849-fw branch April 1, 2026 15:43
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.

3 participants