What is the problem or limitation you are having?

This is a frequent cause of translation lockups -- people modify the content, and an Update Translations commit gets pushed to sync the po file. However, the deleted strings are moved all the way to the end, and if people translates the string that gets modified and those changes are still pending commit from Weblate, it'd cause a conflict since the strings they changed has now went into the unknown.

Describe the solution you'd like

Force Weblate to commit bee-fore we update the translation files and template.

Describe alternatives you've considered

Status quo. Not very sustainable, since the hope is to get a bunch of active translators.

Additional context

Quoting from the PR that this discussion started in:

Untested snippet -- put this in ~/.config/weblate in the CI environment and put in your API key (use a secret, probably):

[weblate]
url = https://hosted.weblate.org/api/
translate = beeware/website

[keys]
https://hosted.weblate.org/api/ = APIKEY

Then:

$ wlc commit

EDIT Reference https://docs.weblate.org/en/latest/wlc.html