spec sheet · code & design

GitHub and Transglot, review locale updates in pull requests.

Install the Transglot GitHub App, select your repository, and map your locale files once. Source changes enter your translation project, and translated files return in a pull request for review.

Repository files and translation requests

Direction: Repository files and translation requests
Plan: Team and up
Scope: locale files in the repository, on push and on demand
Authentication: the Transglot GitHub App installed on your org or account
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 GitHub integration and install the Transglot GitHub App on the account or organization that owns the repository.
connect
Map the locale files
Select the repository and project, then configure the source files, target files and branch.
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
Push a source change or start a sync. Review the translated files in the pull request before merging.
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 to the default branch, the changed source strings are extracted, translated and committed to one stable sync branch, which one pull request tracks. Comment /translate on a pull request and the translations commit onto that pull request's own branch instead. Only target locale files are ever written.

What you can translate and deliver.
Surface	What to expect
Source and scope	locale files in the repository, on push and on demand
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

the Transglot GitHub App installed on your org or account.

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 GitHub integration and install the Transglot GitHub App on the account or organization that owns the repository.
Select the repository and project, then configure the source files, target files and branch.
Push a source change or start a sync. Review the translated files in the pull request before merging.

same project, more possibilities