Integration with GitLab synchronizes source and translation files between your GitLab repository and translation project in Crowdin. All translated and approved files will be automatically pushed as a merge request to the l10n branch in the GitLab repository.
There are two possible options you can choose from. You can either use your GitLab account or GitLab Enterprise account.
To integrate via GitLab Enterprise account you should create an access token. Make sure to select the required scope:
api – Grants complete read/write access to the API, including all groups and projects, the container registry, and the package registry
In the appeared dialog, select your repository and branches that should be translated. It’s recommended to switch Duplicate Strings to Show within a version branch, so identical strings will be hidden between branches. If your source files contain strings with apparent identifiers (keys), it’s better to use a strict version of this option. In other cases, feel free to use a regular one.
Læs mere om Dubletstrenge.
When you work with private integrations (e.g., integrations with self-hosted VCS), you need to add dedicated Crowdin IP addresses to the allowlist to ensure that it operates properly while staying secure.
Read more about IP Addresses.
When translations are finished and your languages are ready to go live, Crowdin sends the merge request with translations to your version control system. For every branch that is under localization, Crowdin creates an additional service branch with translations. We don’t commit directly to the master branch so that you can verify translations first.
Som standard føjes l10n_ til det oprettede tjenestegrensnavn. If necessary, you can easily change it.
By default, sources are not pushed to the repo with translations. Although, if you perform a source text review in your Crowdin project and would like to push the changes made to your source files on Crowdin back to your repo, click Edit, select Push Sources in the integration settings, and click Save.
There are cases when it’s necessary to disable translations from being pushed to the repo temporarily. In this situation, click Edit, clear Push Translations in the integration settings, and click Save. When ready to sync translations with the repo, select the Push Translations, and click Save.
The synchronization is processed every hour automatically. If necessary, you can change the update interval in the integration settings. To configure the synchronization schedule – click Edit, scroll down to the Sync Schedule, set the preferred interval, and click Save.
Not depending on the synchronization settings, the source files’ changes on the repo will still be synced with Crowdin every ten minutes.
When you set up the integration, you select existing repository branches to be added to the Crowdin project. To add future branches from GitLab to Crowdin automatically, create a pattern for the branch names in the integration settings.
Du kan f.eks. tilføje en mønster *funktion i GitLab-Integrationsindstillingerne. Fremtidige grene, som indeholder dette ord i slutningen af titlen, vil i så fald blive føjet til projektet.
For at tilføje et mønster for grennavne, så følg disse trin:
crowdin.yml is the default file name that is used for automatically synchronized branches. To change the default settings, click Edit, specify the preferred name in the Default configuration file name field in the integration settings, and click Save.
For at få integrationen til at fungere, skal du angive, hvilke kildefiler, som skal oversættes, og hvordan Crowdin skal strukturere oversatte filer i dit depot. If you see a red icon with an exclamatory mark next to the service branch name, it means that you didn’t select content for synchronization.
Dette kan gøre på to måder: Online eller manuel oprettelse af en opsætningsfil.
Denne procedure er den samme for alle integrationer med versionsstyringssystemer (VCS). Tjek VCS-integrationer: Onlineopsætning for at få mere at vide om, hvordan man vælger et indhold til synkronisering online.
crowdin.yml should be stored in the GitLab repository along with each separate branch that you want to translate, so Crowdin knows what files exactly should be sent for translations.
It should have the same structure as required for CLI, but your project’s credentials should not be stored in the file’s header for security reasons.
Læs mere om oprettelse af opsætningsfil.
When working with a multiplatform product that has versions for different operating systems, you might want to connect multiple repositories that contain source files for each operating system. In this case, localization resources (e.g., TMs, Glossaries) and translations could be used more efficiently, reducing the time needed for project localization.
To add another repository, follow these steps:
Once the integration is set up, all the related information is stored in the same place – Applications tab > GitLab section. By default, synchronization is processed every hour automatically. Vil du starte synkronisering straks, så klik på Synk nu.
By default, the translations stored on the repo are uploaded to Crowdin during the first synchronization only. To upload translations to Crowdin manually, click on the drop-down toggle on the Sync Now button, and click Upload Translations. The integration will upload existing translations to your Crowdin project.