Crowdin’s integration with GitLab makes source and translation files synchronized with GitLab repository and Crowdin translation project. All translated and approved files will be automatically pushed as a merge request to the l10n branch in GitLab repository.
First, open Project Settings, Integrations tab in Crowdin. Go to the GitLab section. Then you have two options. You can use either your GitLab Account or GitLab Enterprise Account for integration.
To integrate via your GitLab Account you can click Set Up Integration and then authorize the connection with Crowdin on the GitLab side:
To integrate via GitLab Enterprise Account you should create an access token. Make sure to select the required scopes:
Then insert your access token and Base URL into corresponding fields. Click Set Up Integration to proceed.
After the successful integration, a pop-up dialogue would appear in your Project Settings, Integrations tab in Crowdin. Use it to continue the process of integration setup selecting necessary repository and branches that should be translated.
It is recommended to switch the duplicated strings handling to the Show (Recommended for versions) setting, so equal strings will be hidden across the branches.
When translations are finished and your languages are ready to go live, Crowdin sends merge request with translations to your version control system. For every branch that is under localization, Crowdin creates additional service branch with translations. We do not commit directly to the master branch so you can verify translations first.
By default, l10n_ is added to the created service branch name. In case of necessity, it can be easily changed.
When you set up the integration you select existing repository branches that should be added to the Crowdin project. To add future branches from GitLab to Crowdin automatically, create a pattern for the branch names. If a branch name follows a certain pattern, it will be automatically added to Crowdin.
For example, you add a pattern *feature in the GitLab integration settings. In this case, the future branches that contain this word at the end of the title will be added to the project.
To add a pattern for branch names, follow these steps:
To get the integration working, you have to specify which source files should be translated and how Crowdin should structure translated files in your repository. In case, you see a red icon with an exclamatory mark next to the service branch name, this means that you didn’t choose content for synchronization.
There are two ways to do that: configuring online, or manually, creating a configuration file.
This procedure is the same for all integrations with version control systems (VCS). Check VCS Integrations: Configuring Online to get to know how to select content for synchronization online.
Configuration file crowdin.yaml has to be placed in 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 Synchronization Tool, but your project’s credentials should not be stored in the file’s header for the security reasons. Read more about creating a configuration file.
Having completed the process of integration setup, in the Project Settings, Integrations tab, all the information about integration will be stored there. By default, synchronization is processed every 10 minutes automatically. In case, there is a necessity to launch it instantly, click Sync Now.