Integrazione GitLab

Integration with GitLab synchronizes source and translation files between your GitLab repository and translation project in Crowdin. Tutti i file tradotti ed approvati saranno prelevati automaticamente come richiesta di unione al ramo l10n nella repository di GitHub.

Connettere GitLab con Crowdin

There are two possible options you can choose from. You can either use your GitLab Account or GitLab Enterprise Account.

Connecting GitLab Account

  1. Open Project Settings, Integrations tab in Crowdin and click Set Up Integration to integrate via your GitLab Account.

  2. Then authorize the connection with Crowdin on the GitLab side:

Connecting GitLab Enterprise Account

  1. 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
Note: When setting up an integration with an access token, make sure that you have the Maintainer level permission to the necessary repo.
  1. Then insert your access token and Base URL into corresponding fields. Click Set Up Integration to proceed.

  2. 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.

Rami Servizio

When translations are finished and your languages are ready to go live, Crowdin sends merge request with translations to your version control system. Per ogni ramo sotto la localizzazione, Crowdin crea un ramo di servizio aggiuntivo con le traduzioni. 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.

Synchronization Settings

By default, sources are not pushed to the repo with translations. Although, if you perform 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’s 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’s 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’s 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 changes made to the source files on the repo will be still synced with Crowdin every 10 minutes.

GitLab sync settings

Rami da Sincronizzare Automaticamente

Quando configuri l’integrazione selezioni i rami di repository esistente che dovrebbero essere aggiunti al progetto Crowdin. To add future branches from GitLab to Crowdin automatically, create a pattern for the branch names in the integration’s settings.

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.

Per aggiungere un modello per il ramo nomi, segui questi passi:

  1. Click Edit in the GitLab integration section.
  2. In the pop-up dialogue scroll down to the Branches to Sync Automatically.
  3. Nel campo Rami da Sincronizzare Automsticamente, usa i selettori wildcard come ‘*’, ‘?’, ‘[set]’, ‘' ed altri per identificare i rami necessari.
  4. Clicca Salva. Rami da Sincronizzare Automaticamente

Default configuration file name

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’s settings, and click Save.

Default configuration file name

Selezionare Contenuto per la Sincronizzazione

Per fare funzionare l’integrazione, devi specificare quale file risorsa dovrebbe essere tradotto e come Crowdin dovrebbe strutturare i file tradotti nella tua repository. Nel caso che tu veda un’icona rossa con un punto esclamativo vicino al nome del ramo di servizio, questo significa che tu non hai scelto il contenuto per la sincronizzazione.

There are two ways to do that: configuring online or manually by creating a configuration file.

Configurare Online

Questa procedura è uguale per tutte le integrazioni con il sistema di controllo versione (VCS). Controlla Integrazioni VCS: Configurare Online per sapere come selezionare contenuto per la sincronizzazione online.

Creare File Configurazione

Configuration file crowdin.yaml 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 Synchronization Tool, but your project’s credentials should not be stored in the file’s header for security reasons. Leggi di più su creare un file configurazione.

Controllare lo Stato di Sincronizzazione

Once the integration is set up, all the related information is stored in the same place – Project Settings, Integrations tab, GitLab section. By default, synchronization is processed every hour automatically. If you need to launch the synchronization instantly – click Sync Now.

GitLab Sync Now

Uploading Translations from Repo

By default, the translations that are 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 the Crowdin project.

GitLab Upload Translations

Vedi Anche

Questo articolo è stato utile?