Transifex translations: we should not update from the _completed branches
_Originally created by @emmapeel on [#16774 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/16774)_ ey there\! I think we should change the branches from where we pick up our translations coming from transifex. The Tails resources being translated on transifex have usually two branches each on <https://gitweb.torproject.org/translation.git/> For example, the resource translating WhisperBack has: - <https://gitweb.torproject.org/translation.git/log/?h=whisperback> - <https://gitweb.torproject.org/translation.git/log/?h=whisperback_completed> This translations are imported with the ./import\_translations.sh \#\# THE PROBLEM As reported in <https://trac.torproject.org/projects/tor/ticket/26878> , the \\**\_completed branches areonly updated when a resource is completed**\*, so a problem arises when: - A translation is completed - the \_completed branch is updated - There are new strings on the file - the \_completed branch is NOT updated - Some of the translations are done, but not all - the \_completed branch is NOT updated While I welcome help to solve the tor ticket before, my suggestion for Tails is to pull from the normal branch, and use the \_completed branch as a way of seeing the situation of the translation (how many times this file was completed? etc). By not using the \_completed branch, we will be having less outdated translations. Especially on the ‘long tail’ of languages. ### Subtasks - [x] tails/tails#17106 ### Related issues - **Related to** tails/tails#16095 - **Related to** tails/tails#17279
issue