Integration with Azure Repos synchronizes source and translation files between your Azure Repos repository and translation project in Crowdin. All translated and approved files will be automatically pushed as a pull request to the l10n branch in Azure Repos repository.
Open Project Settings, Integrations tab in Crowdin and click Set Up Integration.
Then authorize the connection with Crowdin on the Azure Repos side:
In the pop-up dialogue select your repository and branches that should be translated. It is recommended to switch Duplicate Strings to Show (Recommended for versions), so identical strings will be hidden between branches. Read more about Duplicate Strings.
When translations are finished and your languages are ready to go live, Crowdin sends pull 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. If necessary it can be easily changed.
The synchronization is processed every 10 minutes automatically. If necessary you can change the update interval in the integration’s advanced settings. To configure the synchronization schedule – click Edit, then click Show Advanced Settings.
When you set up the integration you select existing repository branches that should be added to the Crowdin project. To add future branches from Azure Repos to Crowdin automatically, create a pattern for the branch names in the integration’s advanced settings.
For example, you add a pattern *feature in the Azure Repos 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 by 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 should be stored in the Azure Repos 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 security reasons. Read more about creating a configuration file.
Once the integration is set up, all the related information is stored in the same place – Project Settings, Integrations tab, Azure Repos section.
By default, synchronization is processed every 10 minutes automatically. If you need to launch the synchronization instantly – click Sync Now.