Recommendations for handing renamed files.

[CraigSiemens]

Occasionally we'll make a change to our project causing the path of a localized file to change. Either renaming a folder or moving between folders. When that happens, crowdin sees it as one file being removed and a new file being added. We're wondering if there's a recommended way to handle this case so crowdin can treat it as a moved file instead.

Our current workflow is one of the following.

• If a dev remembers
  • They manually upload the "removed" translation file for the "added" file.
• If a dev forgets, either
  • The translation team just goes through all the new stings and re-adds translations.
  • The devs get a message from the translation team some time later asking why there's up to hundreds of new strings all of a sudden. Then the dev manually manually uploads the file.

I was looking at the upload_translations option which seems like it could help in this case, but we're unsure how it would behave for brand new strings. ie. When the git repo contains no or and old translation for a string, but the translation has been updated on Crowdin but not yet downloaded, what would be the resulting translation on crowdin if a upload was done?