Manually trigger msgmerge

[dylankiss]

Describe the problem

We regularly launch a new version of our software and create a new Weblate project for it.
We export the POT files, copy the PO files from the previous version and msgmerge them locally.
It sometimes happens someone fixes something (re-exporting just a POT file) before the sync to the new Weblate project is done, causing out-of-date PO files.

Solution brainstorm

Since Weblate has a msgmerge feature, it would be very convenient if we could trigger it manually (on specific components or projects).

Describe alternatives you have considered

No response

Screenshots

No response

Additional context

No response

[nijel]

If the POT file is in the repository, you should install the msgmerge add-on (see https://docs.weblate.org/en/latest/admin/addons.html#update-po-files-to-match-pot-msgmerge) to automatically update PO files whenever it changes.

If it is not in the repository, the "Update source strings" allows you to trigger it via uploaded file (see https://docs.weblate.org/en/latest/user/files.html#import-methods).

[dylankiss]

We have the msgmerge add-on enabled. The case I'm describing here, is when the PO files don't match the POT file (for any reason) before the Weblate project is created. Having an easy way to make it match it in Weblate (for a whole project at once) would be convenient, instead of having to do a msgmerge locally on every PO file (we have a lot of them).

If we need to do it locally, we need to lock the project (many components), sync the latest changes to GitHub, do the msgmerge locally on all PO files, commit to GitHub, wait for Weblate to update its database, and finally unlock the project again.

[nijel]

I believe the msgmerge add-on will run upon install, so you can install it, and it should trigger the sync.