Clarify how the review process of Weblate influences git commit
We might want to switch from our current setup:
- a user proposes a translation
- once another user votes for the translation it get committed
to latest Weblate’s feature of translation states.
This might be needed in order to be able to build a staging website. (It’ll also involve having weblate use two Git repositories, one to store all translations, one to store only the reviewed translations -> we’ll have to see how to make this happen, likely we’ll have to query it’s database directly and add the corresponding commits.)
However, it seems that these translation states always commit and modify
the PO files. And the states are only stored in Weblate’s DB. This is
what we want to verify.
Doc:
https://docs.weblate.org/en/latest/workflows.html#translation-states
Parent Task: #15075 (closed)
Related issues
- Related to #15365 (closed)
Original created by @u on 15357 (Redmine)