spec sheet · code & design

GitLab and Transglot, keep translations in your merge workflow.

Add your repository credentials and map your locale files in workspace settings. Sync source changes with your project and review the translated files in a GitLab merge request.

Repository files and translation requests

Direction: Repository files and translation requests
Plan: Team and up
Scope: locale files in the repository, on push
Authentication: a project access token and a webhook secret, per project
Get started: Connect from your workspace’s integration settings.

Create your project Setup

code & design

the workflow

Connect your content. Review every language.

Connect once, choose your content and languages, then translate and review in the same project. The steps below show how it works in your tool.

Connect the repository
Open your workspace’s GitLab integration and select a Transglot project.
connect
Map the locale files
Add a GitLab project access token, repository settings and a webhook secret. Configure the source and target locale paths.
files
Sync source changes
A repository event or manual sync brings the configured source files into the project. Translate and review those keys in Transglot.
review
Review the proposed changes
Configure the GitLab webhook, push a source change, and review the translation merge request.
request

Translated locale files return in a pull request or merge request for your team to review.

what moves

What you can translate and deliver.

On a push, target locale files are committed in one atomic call to a stable sync branch and one merge request per link is found or opened, so two quick pushes converge instead of opening a second one. GitLab.com only for now, and there is no /translate comment command yet.

What you can translate and deliver.
Surface	What to expect
Source and scope	locale files in the repository, on push
Translated output	Translated locale files return in a pull request or merge request for your team to review.
Keep in mind	The connector works with the file paths and branch you configure. A translation request is reviewed in your repository before it is merged.

get connected

A few steps to your first connection.

Follow your tool’s setup below: add the connection, choose what to sync, and try it with a small set of content. Your team can keep working in the tools they already use.

What you need

a project access token and a webhook secret, per project.

A Transglot project with its source and target locales configured.
Save credentials in the connection settings so your team can work without copying secrets between files.
Hosted API access requires a paid Transglot plan. AI translation uses your workspace’s word allowance.

Create your project

Open your workspace’s GitLab integration and select a Transglot project.
Add a GitLab project access token, repository settings and a webhook secret. Configure the source and target locale paths.
Configure the GitLab webhook, push a source change, and review the translation merge request.

same project, more possibilities