Github Integration config meltdown

General Questions
1

Hello, why is the integration always pushing english source strings to the Deu files in github? We end end up with these pr’s with a mix of translated strings and english source strings, so we can’t merge.
every single time I set up the project this happens.
I want it so that if no translation has been entered, nothing is pushed to github.
How do i set up the integration to stop this happening? what order do i do everything?
so far, crowdin is creating more work than it is saving for us!
also how do we set it up so we can edit source strings in crowdin? I checked allow push source edits or whatever, and changed a source in the editor, but seeing nothing in github?
thanks!

2

Hi @SiriusVideo ! when setting up the integration for the first time, the system will create the pull request with source texts (expected behaviour since there are no translations yet).

Later, when you add translations to some strings and some stay untranslated, we push the source instead of missing the translation. If you want to avoid this from happening, you may enable export option Skip untranslated strings
as a result, only translated strings will be pushed

editing source strings online is available for the .json files and with Push sources enabled, the system will push those changes to your repo

3

thanks a lot! and the sources are edited in the normal translation editor?

4

Hi @SiriusVideo

The source strings can be edited directly in the Editor or in the Files → Strings tab. But please note that not all source files can be edited online directly in Crowdin. You can find all available formats here: String Management | Crowdin Docs

1 Like
5

thanks @Olena . should work, we use JSON

6

ok, skip untranslated strings it pushing emplty strings to the repo. this seems a common issue, but i can’t seem to find a common cause?

7

when i change a source, it makes me re-do the translation, even when i check keep translation. is this a known issue?

8

Hi @SiriusVideo,

  1. You can check this table to see how the “Skip untranslated strings” export option behaves with different file formats: Crowdin Export Options.

  2. If the key of the string is changed, the string is considered new and accordingly the translations are not preserved. Could you record a short video showing the steps you’re taking? This would help us better understand the issue.