You can effortlessly update resources on GitHub without coding by just pointing and clicking. Through Transifex GitHub integration, you can link a localization project in Transifex to a designated GitHub repository using only the Transifex user interface.
💡Tip: Use our traditional GitHub integration tools described here to communicate with GitHub Enterprise. In this manner, access is not given to an external service for something so important internally.
Installing the GitHub Integration in a Specific Project
To install the standalone integration that connects Transifex and GitHub, you need to perform the following steps:
Go to your project Settings > Integrations > GitHub > Install
You will be redirected to the integration’s authorization page, where:
First, it is necessary to grant permission for the integration to perform modifications in Transifex on your behalf.
Next, you'll need to authorize the integration in your GitHub account. To do this, select the Authorize button and log into your GitHub account (if you haven't already done so).
Available installations will be listed next. To configure your GitHub applications, visit your GitHub settings page using the link available on the page below:
Click Configure once you are redirected to your GitHub account.
Next, select where you want to install the Transifex integration and choose one or multiple repositories to be accessible in Transifex. The owner (admin) of the account must perform the authentication and repository selection on GitHub. You can choose from the following two alternatives:
All repositories. This option lets you link all present and future repositories to your TX project. You can link each repository to a different project in Transifex.
Only select repositories. This option allows you to choose specific repositories to be synced with your TX project(s).
Once you click Install, you will be redirected back to the GitHub integration’s UI. At this point, you can authorize the GitHub integration to access your GitHub account.
Upon clicking Authorize, you will see the installation you executed in the previous steps. In case you installed multiple apps, they will all be listed as shown below:
Select the GitHub account you would like to connect with your project. You are now ready to link a repository.
📝 Important Note: Your privacy and data security are our utmost priority.
File Handling: Rest assured that we will never read, write, or delete any files beyond what is specified in the YAML file. Our scanning process only aims to find matching files based on the provided YAML configuration.
Pull Request Policy: We respect the integrity of the Pull Request system. We will never close any Pull Request not initiated by our integration.
Linking a Specific Project With a GitHub Repository
Clicking on the Link Repository button, the GitHub Integration wizard will pop up to manage the setup.
Select your Repository
On the wizard's first step, select the GitHub repository and branch to sync with the project. The available repositories listed are the ones you authorized when you installed the Transifex app on the GitHub account you used for the integration. At this point, the GitHub integration works on top of a single branch.
You can find more information about the multi-branching feature here.
📝 Note: If your workspace contains over 100 repositories, the repository selection dropdown will be replaced with a text input field, allowing you to quickly type and find the repository you need.
To select a repository, type the repository’s slug in the following format:
account/repository_slug.
Select files
When you finish this step, click Next to set up the repository files related to localization. There are two ways to select what GitHub files will be synced with your Transifex project:
The first is through a YML config file called “transifex.yml” (but you can name it as you wish). This file will be hosted in your GitHub repository. You can check the following sections for more details:
By default, the integration looks for this file on the root of the branch repo selected in the previous step. However, you can store the file in any folder of your choice. Before proceeding with the wizard's next step, make sure that this file is available in your repo. After that, press "Apply" to preview your file within the Transifex wizard:
The second option is to add the configuration directly in the integration using the text box provided. You will be notified if the configuration is valid as you type.
Regardless of the synchronization option you select for your files, you can validate the detected files based on the specified paths in your configuration by selecting the "Test configuration" button. After you complete it, you can click the Next button to establish a connection between your Transifex project and your GitHub repository and branch.
📝Note: Whenever your config file is updated in your GitHub repository or from within the integration, Transifex is notified, and a sync process between the two systems is triggered automatically.
Whenever new files are added to the configuration file, new resources will be created in Transifex that include any translations obtained from GitHub. These resources will be identified by a unique slug. The GitHub repository and branch path will be added as categories for these resources.
Regarding existing resources that have already been synchronized with GitHub, if translations are detected in your GitHub repository and no translations for that language exist in Transifex, these newly detected translation files will be sent to Transifex.
Sync content
By clicking the Next button, you will be directed to the last step of the configuration, where you will establish the mechanism for synchronization between Transifex and GitHub.
Pulling content from your repository to Transifex.
Whenever any changes are made to the designated branch of a GitHub repository, the process of pulling content from that branch happens automatically. This means that any new code or updates pushed to the repository will be automatically incorporated into the project. This automated process saves significant time and effort, as it eliminates the need for manual updates or synchronization of the code.
Pushing content from Transifex to your repository.
You can decide when and how your localized content is pushed to your repository.
When to push your localized content to GitHub depends on the progress of your localization process. You can decide when to push your translated content to your repo; you have the following options to set this up:
100% translated
100% reviewed
100% proofread
custom
Below, you'll read more about these options.
When a target language reaches 100% of the translation work done.
When you choose to push your content to your repository using this option, it means that Transifex will only push a file's translations once this file has all its strings translated in a specific target language; it will only push the translations of this language to the repository; and it'll not push the translations of target languages that have less than 100% of completion.
For example, if you have a file with the following translation progress, only the translations of Afrikaans(af) and Greek(el) will be sent to your repository, and the Spanish(es) translations will be ignored.
When a target language reaches 100% of reviewed strings.
When you choose to push your content to your repository using this option, it means that Transifex will only push a file's translations once this file has all its strings reviewed in a specific target language; it will only push the translations of this language to the repository; and it'll not push the translations of target languages that have less than 100% of reviewed strings.
For example, if you have a file with the following translation progress, only the translations of Afrikaans(af) will be sent to your repository, and the Spanish(es) and Greek(el) translations will be ignored.
When a target language reaches 100% of proofread strings.
When you choose to push your content to your repository using this option, it means that Transifex will only push a file's translations once this file has all its strings proofread in a specific target language; it will only push the translations of this language to the repository; and it'll not push the translations of target languages that have less than 100% of proofread strings.
For example, if you have a file with the following translation progress, only the translations of Greek(el) will be sent to your repository, and the Spanish(es) and Afrikaans(af) translations will be ignored.
Push content according to a Custom threshold (<100%)
If you need your translations to reach GitHub faster without waiting for languages to be fully completed, you can set a less than 100% custom threshold and select the desired translation status (translated, reviewed, proofread).
📝Note: if a language is already translated/reviewed/proofread and translations are updated in Transifex, the updated translations will automatically be sent to your repo.
For example, if you have a file with the following translation progress and define the custom threshold to 60% translated, only the translations of Greek(el) and Afrikaans(af) will be sent to your repository, and the Spanish(es) translations will be ignored.
You can also define how your translation content reaches your repository; below, you'll find the option you have to set up the way the translations in Transifex hit your repository. You can choose between:
Create a Pull Request
Commit directly
Below, you'll find more information about these options:
Create a Pull Request
This will create a new branch with the localized content and open a PR on the branch that you can later merge directly from GitHub. However, if an open PR already exists containing previous translations, it will be updated with the latest ones.
Content grouping
You can group PRs, particularly when dealing with numerous target languages in your project and resources requiring localization. The following grouping options are available:No grouping - This creates separate PRs for each resource and language combination.
By resource - The PR will contain translations in all target languages for a single resource.
By language - The PR will contain translations in a specific language for all resources.
All resources and languages - This creates a single PR that includes translations for all resources and all target languages.
Commit directly for branches associated with the multi-branch feature
Enabling this option allows you to customize how translation updates are pushed to branches associated with the multi-branch feature while keeping the PR option for your default branch. Please note that this option is available exclusively when the Multi-branching option is enabled.
Commit directly. Commit changes directly to the selected branch.
📝Things to note when using Pull Requests
Suppose the translation or review percentage falls below the set threshold in Transifex, and a PR has already been opened in your repository. In that case, we'll automatically close the PR to ensure no outdated translations remain pending for your review.
If a PR is created based on the condition that x% of the language is translated and the setting is later updated to y% for review or proofreading, we'll close the existing PR and open a new one once the new conditions are met. This ensures that your repository always has the latest and most accurate translations.
Additionally, in this tab of the GitHub integration wizard, you'll find some optional settings. To learn more about them, visit the section Optional Settings in the Sync content tab.
Once you complete the setup, click "Save & Sync" to initiate the synchronization process between GitHub and Transifex.
⚠️Warning: In case your branch is protected, you either have to remove the protection of that branch as described here or change the integration settings to create a PR instead of committing directly to the branch.
Optional settings in the Sync content tab
When configuring the link settings between your Transifex project and your GitHub repository, you'll come across a section called "Sync Content".
In this section, you'll find various alternative features that can be used to set up the way your translated content reaches your repository:
Add a prefix to the commit message.
Add a prefix in the Pull Request title.
Receive updates for source files.
Add an interval between commits.
In this article, you'll find the specifications of such features.
Add a Prefix Your Commit Message
If you have configured GitHub Actions in your repository and want to exclude commits made by the Transifex GitHub integration from workflow runs, you can add a prefix to the commit message. This will also improve readability in your workflow.
For example, if I add the prefix "TRANSLATION-UPDATE" and save this setting update:
The commits sent to GitHub will show this prefix.
Add a prefix in the Pull Request title.
If you have configured GitHub Actions in your repository and want to admit only certain Pull Requests in your workflow, you can add a prefix to the Pull Requests title; this will also improve readability in your workflow.
For example, if I add the prefix "NEW-PR-TITLE" and save this setting update:
The Pull Requests sent to GitHub will show this prefix.
Receive updates for source files.
Enabling the feature Receive updates for source files means that you can sync any changes you make to your source file in Transifex with your repository without any manual intervention. This can save you a considerable amount of time and effort. Additionally, it ensures that the most up-to-date version of your project is always available to your users.
It's important to note that not all file formats support automatic updates. Therefore, it's advisable to consult the article on Updating Content to obtain more information about which file formats can have their source updated in Transifex.
Add an interval between commits.
If you want to avoid having many commits of the same translation file flooding your repository for every single update of translations, you can set a time interval to group those updates in one commit.
By setting a time interval in minutes (up to a maximum of 60 minutes), you can control how often translation updates get pushed to your repository so that you can manage your translation changes in your repository more effectively.
For example, let's say that you've set the commit interval to 10 minutes. Within those 10 minutes, you make several translation edits in a resource file. Instead of individual commits for each change, you'll receive a single commit after the 10-minute interval expires, including all the latest updates. If you continue to edit the same translations, a new commit will be generated after another 10 minutes, grouping all changes made during that time.
📝Note
Commits are synced for the resource/language pair. This means that if you make changes to 2 language translations during the interval time, you will see on Github 2 separate commits for that resource. The same behavior will be observed if you make changes to 2 different resources for the same target language.
YAML Configuration Parameter Descriptions
The following are the parameters that are used for the YAML Configuration:
git: This is what the top line of your configuration file should contain.
filter_type: The three valid values are
dirfor directory,file, anddynamic.source_file: Only used for the
filefilter_type. This points to the location of the source file. The location should not start with a forward slash and should not be surrounded by double or single quotes.source_file_dir: Only used for the directory (
dir) filter_type. Works the same as source_file.source_files_expression: Only used for the
dynamicfilter_type. Works the same as source_file.source_file_extension: Only used for the directory (dir) filter_type.
file_format: This sets the type of resources in your project, e.g., PO. See the File formats for details about the i18n type of each format available.
source_language: This is the source language of your project, such as
en(for English). This is the language you selected when you created your project.translation_files_expression: A path expression that reflects your translation files' file/directory structure. The expression must contain the <lang> keyword, denoting where the file paths differentiate per language, e.g.,
translations/po/<lang>.po; the appropriate target language file format will automatically replace the <lang> keyword.The expression should not start with a forward slash and should be surrounded by single quotes.
mode: This setting allows you to choose which download mode a translation file will use. This mode affects how translations are retrieved and varies depending on the file type. Please refer to the specific file format's specification page for details about each specific download mode.
⚠️Warning: XCSTRINGS files can't take advantage of this option at this time.
language_mapping: If you use language codes other than the standard ISO ones (ISO 639-1, ISO 639-2, or ISO 639-3), the integration lets you set up custom one-to-one language mappings. You'll need to add a language_mapping section to the YAML configuration file.
settings:
language_mapping:
REMOTE_CODE: LOCAL_CODEThe REMOTE_CODE is the language code supported by Transifex. And the LOCAL_CODE is your language code.
📝 Mapping locales will only impact the filenames of the translation files, aligning file naming conventions with your selected locale mappings.
The configuration follows a YAML syntax, and users can define a list of individual files or use regular expressions to match multiple files simultaneously. Illustrated examples can be found below:
pr_branch_name: If you want to specify the name used for a PR when pushing translations back to GitHub, you can use this parameter under settings like the following example. Please note that <br_unique_id> is a string hash automatically generated by the system.
ignore_dirs: If you want to exclude one or more than one directory/folder (include absolute paths when using this parameter), then you can include this parameter in your configuration file as follows:
ignore_files: If you want to exclude one or more than one localization file (include absolute paths when using this parameter), then you can include this parameter in your configuration file as follows:
You can have multiple entries beneath the opening "filters:" keyword for different source file types or locations. Each entry begins with "- filter_type: ".
Check the section More Examples of YAML Configurations for samples.
More Examples of YAML Configurations
Syncing a Single File
filters:
- filter_type: file
file_format: PO
source_file: locale/example.po
source_language: en
translation_files_expression: 'Translations/<lang>/'
Syncing Multiple Files of a Single File Type
filters:
- filter_type: dir
file_format: STRINGS
source_file_extension: strings
source_language: en
source_file_dir: locale/DirTest
translation_files_expression: 'Translations/<lang>'
Syncing a Single File Using a Specific Download Mode
filters:
- filter_type: file
file_format: YML
source_language: en
source_file: test.yml
translation_files_expression: 'Τranslations/target_<lang>.yml'
mode: onlytranslated
⚠️Order Matters: In cases where there are two file filter configurations for source and translation files within the same directory, prioritize the more specific filter by placing it first. The following example illustrates this.
Example 1
Example 1
filters:
- filter_type: file
file_format: YML
source_language: en
source_file: config/locales/simple_form.en.yml
translation_files_expression: 'config/locales/simple_form.<lang>.yml'
- filter_type: file
file_format: YML
source_language: en
source_file: config/locales/en.yml
translation_files_expression: 'config/locales/<lang>.yml'
Example 2
Example 2
filters:
- filter_type: dir
file_format: STRINGS
source_file_extension: strings
source_language: en
source_file_dir: locale/DirTest
translation_files_expression: 'Translations/<lang>'
- filter_type: dir
file_format: KEYVALUEJSON
source_file_extension: json
source_language: en
source_file_dir: locale/DirTest
translation_files_expression: 'Translations/<lang>'
Syncing Multiple Files, Excluding Specific Paths/Localization Files
filters:
- filter_type: dir
file_format: KEYVALUEJSON
source_file_extension: json
source_language: en
source_file_dir: localization_project/
translation_files_expression: 'localization_project/translations/<lang>/'
ignore_dirs:
- localization_project/path2/
- localization_project/path3/
ignore_files:
- localization_project/path1/example2.txt
- localization_project/path1/example4.txt
Syncing Files With a Specific Branch Name and With Language Mapping
filters:
- filter_type: file
file_format: STRUCTURED_JSON
source_language: en
source_file: 'locale/example.json'
translation_files_expression: 'Translations/<lang>/example.json'
settings:
pr_branch_name:
tx_translations_<br_unique_id>
language_mapping:
es_419: es-419
pt_BR: pt-br
zh_CN: zh-cn
zh_TW: zh-tw
Examples of the dynamic filter type (Ignore_dirs and Ignore_files are also supported in this filter type)
Example 1:
filters:
- filter_type: dynamic
file_format: PO
source_language: en
source_files_expression: folder/<file>.po
translation_files_expression: 'locale/<lang>/<file>.po'
Examples of possible source file matches:
Example 2:
filters:
- filter_type: dynamic
file_format: PO
source_language: en
source_files_expression: <dir>/<file>.po
translation_files_expression: '<dir>/<lang>/<file>.po'
Examples of possible matches:
Other examples of filter_type: dynamic
Example 1
Example 1
filters:
- filter_type: dynamic
file_format: PO
source_language: en
source_files_expression: docs/guides/<dir>/source/<file>.md
translation_files_expression: <lang>/<dir>/translations/<file>.md
Example 2
Example 2
filters:
- filter_type: dynamic
file_format: PO
source_language: en
source_files_expression: docs/guides/<dir>/source/<file>.md
translation_files_expression: <lang>/<dir>/translations/<file>/product_feature_A.md
📝Note: In YAML, it's essential for the "source_file" to be specified as an absolute path rather than a relative one. This is because GitHub integration always begins its search from the repository's root directory. As mentioned, the .yml file can be located anywhere within the repository.
💡Tip
Looking for more help? Get support from our Transifex Community Forum!
Find answers or post to get help from Transifex Support and our Community.