Skip to content

Conversation

@dylankiss
Copy link
Contributor

@dylankiss dylankiss commented Dec 22, 2025

We updated the PO files by taking the version from 19.0 and msgmerge them with the latest POT file.

Related: odoo/odoo#241030
Related: https://github.com/odoo/enterprise/pull/102739
Related: odoo/design-themes#1201
Related: odoo/documentation#15825

@robodoo
Copy link
Collaborator

robodoo commented Dec 22, 2025

This PR targets the un-managed branch odoo/industry:saas-19.1, it needs to be retargeted before it can be merged.

@vava-odoo
Copy link
Collaborator

@robodoo delegate+

@robodoo
Copy link
Collaborator

robodoo commented Dec 23, 2025

Branch saas-19.1 is not within my remit, imma just ignore it.

@vava-odoo
Copy link
Collaborator

@robodoo help

@robodoo
Copy link
Collaborator

robodoo commented Dec 23, 2025

Pull request status dashboard

@robodoo
Copy link
Collaborator

robodoo commented Dec 23, 2025

Currently available commands for @vava-odoo:

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
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)
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
override=<...> marks overridable statuses as successful
check fetches or refreshes PR metadata, resets mergebot state

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

@robodoo
Copy link
Collaborator

robodoo commented Dec 23, 2025

@vava-odoo I didn't know about this PR and had to retrieve its information, you may have to re-approve it as I didn't see previous commands.

@vava-odoo
Copy link
Collaborator

@robodoo delegate+

We updated the PO files by taking the version from 19.0 and `msgmerge`
them with the latest POT file.
@dylankiss dylankiss force-pushed the saas-19.1-update-i18n-dyki branch from 7665bd8 to ea4e190 Compare December 23, 2025 20:53
@vava-odoo
Copy link
Collaborator

@robodoo override=ci/industry
19.1 is red for other reasons

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants