Git integration with PTC

Git integration connects PTC (Private Translation Cloud) directly to your GitHub, GitLab, or Bitbucket repository, so your resource files are translated where your code already lives. Instead of exporting strings, translating them elsewhere, and importing the results, you keep localization inside the pull-request workflow your team already uses.

Git integration is a Pro feature. It becomes available when you activate Pay-As-You-Go.

How continuous translation through Git works

Once you connect a repository, PTC watches the resource files you choose and turns every change into finished translations:

• You point PTC at your repository and select the branches and resource files to monitor, along with your source and target languages. PTC uses the source language to pick the right engine and to skip strings that should stay untranslated.
• PTC detects new and changed strings whenever you push to a monitored branch.
• PTC translates the updated strings and reviews the result, then opens a pull or merge request containing the translated files.
• You review and merge the request like any other change. PTC keeps monitoring and opens a new request whenever your text changes again.

The result is continuous localization: your translations track development instead of piling up into a separate task before each release.

Localization stays in the review workflow you already use

PTC delivers translations as pull or merge requests, not as files in a separate portal you have to reconcile by hand. Your team reviews the change, runs the same checks it runs on any branch, and merges when ready. Because PTC reviews each translation in context and returns it publish-ready, most requests can be merged without a separate language QA pass. See visual translation review for how that review works.

Translations stay in sync with every commit

After the first merge, PTC continues to monitor your repository. When you add or change strings, it opens a new request with just those updates. When you add new resource files, you can ask PTC to rescan the repository and pick them up. If a translation needs to fit a tight space, PTC can re-translate it within a translation length limit, so a longer language does not break your layout.

Set up Git integration on GitHub, GitLab, or Bitbucket

The workflow is the same on every platform; only the way you create an access token and connect the repository differs. Each guide walks through authentication and connection for that platform:

• GitHub integration with PTC connects a GitHub repository and translates through pull requests.
• GitLab integration with PTC connects a GitLab project and translates through merge requests.
• Bitbucket integration with PTC connects a Bitbucket repository and translates through pull requests.

What you need to connect a repository

To set up Git integration, you give PTC the URL of your project in the repository and authorize access with an access token (recommended) or by signing in. PTC detects which platform you are using, verifies the access it has, and then lets you choose the branches to monitor and the languages to translate into. The exact token type and permissions are covered in each platform's guide above.