spec sheet · code & design

Bitbucket and Transglot, bring locale changes to your repository.

Add your repository credentials and map your locale files in workspace settings. Bring source changes into your project and review translated files in a Bitbucket pull 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 repository or workspace access token and a webhook secret
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 Bitbucket integration and select a Transglot project.
connect
Map the locale files
Add the repository or workspace access token, repository settings and a webhook secret. Configure 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 Bitbucket webhook, push a source change, and review the translation pull 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 pull request per link is found or opened. Your default branch is never touched, and the source file is never pushed back.

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 repository or workspace access token and a webhook secret.

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 Bitbucket integration and select a Transglot project.
Add the repository or workspace access token, repository settings and a webhook secret. Configure source and target locale paths.
Configure the Bitbucket webhook, push a source change, and review the translation pull request.

same project, more possibilities