Setup
Get GitHub running
Three steps, no migration. Point it at your project and the first keys land in the dashboard.
- InstallAdd the package or the config block. Nothing else in your build changes.
- Connect your projectUse the org/project identifier from your dashboard. Keys and languages come from there, not from a local file you have to keep in sync.
- ShipPublish once and every locale is a static file on the edge. Copy changes go live without a new deploy.
Surface
What GitHub gives you
The exact commands, tools and paths you get. Names are what you type, not marketing labels.
initial_importFirst connect: your existing translation files are read and become keys.
source_syncA push to your default branch updates the source language automatically.
cdn_uploadApproved translations are written to the edge as static files.
batch_publishPublishing sends the batch back to your repository as a pull request or a direct commit.
Where it fits
How GitHub works inside Better
Detect
Pull source strings from your codebase or connect your GitHub repository. Keys arrive in Better with structure and context intact.
Review
Run AI translation, assign human reviewers, and gate approval before any change reaches production. Everything auditable in one place.
Ship
Publish to the CDN edge or push translations back to GitHub. Copy changes go live without triggering a new app deploy.
Developer-first workflow
Localization lives close to your code — reviewable in pull requests, version-controlled, and part of your existing CI and deploy pipeline.
Less operational drift
Centralize translation updates, review sign-off, and delivery in one workflow instead of spreading work across separate tools and scripts.
Controlled rollout
Decouple translation publishing from code releases. Ship copy changes on your schedule without waiting for the next deploy window.
Questions
Before you connect it
Next
Connect GitHub today
Free to start. Add the integration, publish once, and see the copy change without a release.