GitHub (TMS)

Content is machine translated from English by Phrase Language AI.

Available for

Team, Business and Enterprise plans

Get in touch with Sales for licensing questions.

Available for

Ultimate and Enterprise plans (Legacy)

Get in touch with Sales for licensing questions.

Tip

For information about GitHub integration in Phrase Strings, refer to GitHub (Strings).

GitHub connector allows the downloading of source files and uploading of target files directly to/from the GitHub repository.

The connector uses the GitHub API to implement the integration. The connector allows access to all repositories associated with a GitHub account. GitHub account authentication can also be made in the GitHub App.

Use Cases

There are a number of use cases for the connector:

Project managers can add files directly to projects from an online repository.
Set up the submitter portal to allow Submitters to add files to requests directly from the online repository.
Use automated project creation (APC) to have new projects automatically created when a change in file size is detected in monitored files or a folder.
- This connector supports absolute path setting. Target translation files can be stored only in the same branch as the source file.
Set up continuous jobs to have selected files monitored for changes.

GitHub (Beta)

Note

The connector is in beta as of June 2026.

Authentication

The GitHub (Beta) connector uses the GitHub App installation token rather than an individual user account. Tokens are short-lived and renew automatically. If a user leaves the organization or loses repository access, the connector continues to work.

The GitHub (Beta) connector supports GitHub App authentication only. The OAuth option from the original connector is not supported.

Export

The GitHub (Beta) connector batches all files from a single export into one commit and one pull request, so CI runs once per export regardless of file count.

Files are batched into a single commit when all content shares the same repository owner, repository, and branch.

If the APC is configured to upload files as they are individually completed, each file will be committed separately rather than batched.

Commit messages are generated automatically and cannot be customized. If exporting as a pull request, the pull request name and target branch name can be customized.

Known limitations

The connector can list, download, and upload files only. Deleting or moving files in GitHub is not supported. Any deletions or renames must be done directly in GitHub.
File listing may not work correctly for repositories with more than 50,000 files due to GitHub API limitations.
GitHub Enterprise Server is not currently supported.
The new connector does not support the OAuth flow from the legacy connector. If your organization has restrictions on GitHub App installations, resolve those before migrating.

Migration to the new GitHub (Beta) connector

Automated migration is not possible due to the change in authentication model.

Prerequisites:

Admin access to your GitHub organization to install a GitHub App. Install it at the organization level so it covers all repositories your APCs monitor.
Existing APC settings visible (keep the old connector open in a second tab).
A test branch or non-production repository to validate before switching live workflows.

Follow these steps:

Install the Phrase GitHub App.
1. In Phrase TMS, from the Settings page, scroll down to the Integrations section.
2. Click on Connectors.
  
  The Connectors page opens.
3. Click New connector.
  
  The Create connector page opens.
4. Change the Type to GitHub 2.0.
5. Click Connect.
  
  Phrase redirects to GitHub to authorise the Phrase GitHub App.
6. On GitHub, select the organization or account and the repositories to grant access to, then confirm the installation. Include every repository currently monitored by the existing connector(s).
  
  GitHub redirects to Phrase automatically.
7. Select the user or organization account to connect.
Create a new connector.
1. In Phrase TMS, from the Settings page, scroll down to the Integrations section.
2. Click on Connectors.
3. Click New connector.
4. Select the GitHub App installation set up in the first step.
5. Copy settings from the existing connector:
  - Repository and branch
  - Subfolder path (if using subfolder monitoring)
  - File filter regex (if configured)
  - Export mode: direct commit or pull request, and target branch
  - Pull request name and target branch name (if using PR mode)
  It is possible to create multiple connectors under the same GitHub App installation, each with independent settings.
Recreate existing APCs using dry-run mode.

Do not delete or disable the existing APCs yet.
1. Create new APCs pointing to the new connector, mirroring the existing APC configuration.
2. Enable dry-run mode on each new APC before activating it. Dry-run mode scans the repository and matches files without triggering translation jobs.
3. Review the matched files. Confirm the scope matches what the existing APC monitors.
Validate with a test export.
1. Make a small change to a file in the monitored scope.
2. Trigger an export through the new connector.
3. Confirm:
  - A single commit is created (not one per file).
  - The commit appears under the GitHub App identity, not a personal account.
  - CI runs once, not once per file.
Switch live workflows.

Once validation passes:
1. Disable the APCs on the legacy connector.
2. Enable the APCs on the new connector (remove dry-run mode).
3. Monitor for one or two export cycles before decommissioning the legacy connector.
Decommission the legacy connector.

After confirming the new connector is stable:
1. Delete the old APCs.
2. Delete the legacy connector from Settings → Connectors → GitHub (Legacy).
3. Optionally, revoke the OAuth token for the user account that was used by the legacy connector.

GitHub Settings (legacy)

No changes are required.

Phrase TMS Settings

Important

If accessing from a custom domain (ex. mydomain.phrase.jp), open an incognito browser window and log in via cloud.memsource.com or us.cloud.memsource.com to apply the authentication required for the creation or saving of the connector. After saving, the connector can be accessed via the custom domain.

From the Settings page, scroll down to the Integrations section.
Click on Connectors.

The Connectors page opens.
Click New connector.

The Create connector page opens.
Change the Type to GitHub and provide a name for the connector.
Optionally select Export translations as pull requests and provide a Pull request branch.
If required, select Use Github app to display the Phrase GitHub app URL and import/export files using the GitHub app authorization flow:
1. Click the link to open the Phrase App Connector official page in a new tab: https://github.com/apps/phrase-app-connector-eu (EU data center) or https://github.com/apps/phrase-app-connector-us (US data center).
2. Install the Phrase GitHub app to the target GitHub account.
  
  Note
  
  If the GitHub app is not installed to the user’s target GitHub account, only public repositories will be visible to the GitHub connector.
3. Complete the installation procedure by selecting any private repositories that will be visible and accessible for the GitHub connector.
4. Go back to the Phrase Connectors/Create page to authorize the GitHub app and connect to GitHub.
Click Connect to GitHub. If not connected using the GitHub App, a popup window or a new tab will appear requesting authorization.
Provide a Commit message if required.
Click the Authorize Phrase button.

If using the GitHub app, click the Authorize Phrase App Connector button.

If successful, the window/tab will disappear and a small checkmark appears next to the Connect to GitHub button.
Click Save.

The connector is added to the list on the Connectors page.

Important

If the GitHub connector is created using the GitHub app authorization flow, it is not possible to change the authorization method after saving the connector settings.