Go to your project Settings > Integrations > GitLab > Install

You will be redirected to the integration’s authorization page, where:

Once you click Authorize, you will be redirected back to the GitLab integration’s UI. At this point, you can authorize the GitLab integration to access your GitLab account.

Upon clicking Authorize, you will see all accounts for which you have to write permissions (i.e., Developer role or above):

Select the GitLab account you would like to connect with your project. You are now ready to link a repository.

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 GitLab 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, ensure 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.

Push translations to GitLab when a language becomes:

Additionally, if a language is already translated/reviewed/proofread and translations are updated in Transifex, the updated translations will automatically be sent to your repo.

Push translations to GitLab:

git: This is what the top line of your configuration file should contain.

filter_type: The three valid values are dir for directory, file, and dynamic.

source_file: Only used for the file filter_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 dynamic filter_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. Please take a look at 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.

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.

The REMOTE_CODE is the language code supported by Transifex. And the LOCAL_CODE is your language code.

pr_branch_name: If you want to specify the name used for a PR when pushing translations back to GitLab, you can use this parameter under the settings like in 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: