Once your locale files live in a GitHub repo, Globalize can keep them translated automatically. When you push new source text, Globalize opens a pull request with the translations already filled in. You review and merge — nothing is pushed to your main branch directly.
This guide covers connecting a repo through an AI agent using the MCP server.
Before you start
- Install the Globalize GitHub App on the account or organisation that owns the repo. If it isn't installed yet, the agent can start the install and hand you a link to approve in your browser.
- Push your latest code first. Globalize reads the repository from GitHub, so any locale files that only exist locally won't be seen.
Steps
- Find your installation. The agent lists your GitHub App installations and picks the one that owns your repo.
- Detect the repo. The agent scans it and reports what it found — your framework, the locale file pattern (for example
messages/{locale}.json), the file format, and your source and target languages. This confirms Globalize will read the right files. - Connect it. The agent links the repo to your project and registers a webhook. Your existing translations can be imported as final so they aren't re-translated.
- Push new text. Add a new string to your source locale file and push to your connected branch.
- Review the PR. Within about a minute, Globalize opens a branch like
globalize/translations-mainwith a pull request adding the new keys to each target language. Merge when you're happy.
Good to know
- The pull request is scoped to what changed. New keys get translated; your reviewed translations are left alone.
- Locale files always live in your repo. You own them, and every change goes through a PR you approve.
- If a translation reads too formal or too casual for your brand, set a per-language style guide (for example, "use informal address") so future translations match your voice.