This solves the problem for us! Thank you very much for the answer.
My tests show that deleting a branch does indeed make the duplicate become the new master string.
The reason why it was not working before is because I deleted feature branch from Crowdin before the newly merged to our GH main branch source strings were pushed to Crowdin. We will adjust our deployment scripts to account for that.
But still I have a question:
Imagine there are 2 branches - main
(root Crowdin branch) and feature_1
(same name in Crowdin), where in feature_1
branch lots of new strings were added and pre-translated using AI without approvals.
- Then on GH repo side
feature_1
is merged intomain
branch - GH actions automation runs
crowdin push sources
from thatmain
branch - immediately after
crowdin branch delete feature_1
is run to deletefeature_1
from Crowdin
Is it guaranteed that at the moment of uploading sources (step 2 above) the duplicates are properly registered so that deleting a branch (step 3) won’t remove the translations completely?