Integração GitHub

Integration with GitHub synchronizes source and translation files between your GitHub repository and translation project in Crowdin Enterprise. Todos os ficheiros traduzidos e aprovados, serão automaticamente, enviados como um pull request para o ramo l10n no repositório do GitHub.

Connecting GitHub with Crowdin Enterprise

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

Connecting GitHub Account

  1. Open your Crowdin Enterprise project and go to Applications > System.
  2. Click on GitHub in the Integrations list.
  3. Click Set Up Integration to integrate via your GitHub account.
  4. Then authorize the connection with Crowdin Enterprise on the GitHub side.

Caso o repositório que precisas é privado, e tens acesso limitado ou nenhum, pergunta ao proprietário do repositório para fornecer-te o Token de Acesso. Afterward, click Use personal access token and insert the token into the Token field and click Set Up Integration.

Connecting GitHub Enterprise Account

  1. To integrate via GitHub Enterprise account, you should create an access token. Make sure to select the required scopes:

    • repo – Full control of private repositories
    • admin:repo_hook – Full control of repository hooks
  2. Click on GitHub Enterprise in the Integrations list.
  3. Then insert your access token and Base URL into corresponding fields. Click Set Up Integration to proceed.

Selecting Repository

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.

Read more about Duplicate Strings.

When you work with private integrations (e.g., integrations with self-hosted VCS), you need to add dedicated Crowdin Enterprise IP addresses to the whitelist to ensure that it operates properly while staying secure.

Read more about IP Addresses.

Ramos de Serviço

When translations are finished and your languages are ready to go live, Crowdin Enterprise sends the pull request with translations to your version control system. For every branch that is under localization, Crowdin Enterprise creates an additional service branch with translations. We don’t commit directly to the master branch so that you can verify translations first.

By default, l10n_ is added to the created service branch name. If necessary, you can easily change it.

Synchronization Settings

By default, sources are not pushed to the repo with translations. Although, if you perform source text changes in your Crowdin Enterprise project and would like to push the changes made to your source files on Crowdin Enterprise 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 Enterprise every ten minutes.

Branches to Sync Automatically

When you set up the integration, you select existing repository branches to be added to the Crowdin Enterprise project. To add future branches from GitHub to Crowdin Enterprise automatically, create a pattern for the branch names in the integration settings.

For example, you add a pattern *feature in the GitHub 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:

  1. Click Edit in the GitHub integration section.
  2. In the appeared dialog, scroll down to the Branches to Sync Automatically.
  3. In the Branches to Sync Automatically field, use wildcard selectors such as ‘*’, ‘?’, ‘[set]’, ‘' and others to identify the necessary branches.
  4. Clica em Guardar.

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

Selecionar Conteúdo para Sincronização

Para obter a integração a funcionar, deves especificar quais ficheiros de origem devem ser traduzidos e como o Crowdin Enterprise deve estruturar ficheiros traduzidos no teu repositório. 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.

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

Configuração Online

Este procedimento é o mesmo para todas as integrações com sistemas de controlo de versão (VCS). Verifica Integrações VCS: Configuração Online para saber como selecionar o conteúdo para sincronização online.

Criar Ficheiro de Configuração

Configuration file crowdin.yml should be stored in the GitHub repository along with each separate branch that you want to translate, so Crowdin Enterprise 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ê mais sobre criar um ficheiro de configuração.

Working with Multiple Repositories within One Project

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:

  1. Open your Crowdin Enterprise project and go to Applications > System.
  2. Click on GitHub in the Integrations list.
  3. Click Add Repository.
  4. Configure the integration with the new repository according to your needs and preferences.

Verificar o Estado de Sincronização

Once the integration is set up, all the related information is stored in the same place – Applications > System > GitHub section. The synchronization is processed every hour automatically. If you need to launch the synchronization instantly – click Sync Now.

GitHub Sync Now

Uploading Translations from Repo

By default, the translations stored on the repo are uploaded to Crowdin Enterprise during the first synchronization only. To upload translations to Crowdin Enterprise manually, click next to the Sync Now button, and click Upload Translations. The integration will upload existing translations to your Crowdin Enterprise project.

Q&A

Q: What should I do if my repository becomes a part of the GitHub organization?
A: To continue using GitHub integration in Crowdin Enterprise, follow these steps:

  1. Go to Authorized OAuth Apps in your GitHub account.
  2. Find Crowdin OAuth App in the list and revoke its access.
  3. Set up the GitHub integration in your Crowdin Enterprise project again using the instructions above.

Ver Também

Este artigo foi útil?