Documentation

GitHub sync

Connect a repository and let ParlanceKit open pull requests with your translations.

Repository sync fetches your source file, translates what has changed since the last run, and opens a pull request with the updated translation files. Nothing merges without your review, and your translated files live in your repository — not on our servers.

Connect

1. In Settings, connect GitHub and authorize the ParlanceKit app for the repositories you want.
2. Add a repository configuration: the source file path, a target file pattern, and your target languages.
3. Optionally link a saved configuration so tone, glossary, and context apply to every sync.
4. Press Sync. The job is queued and a worker picks it up.

Where settings come from

A sync resolves its translation settings in this order. The first source that exists wins.

1. parlancekit.config.json committed at the root of the repository.
2. The configuration linked to the repository in the dashboard.
3. Built-in defaults — neutral tone, default formality, your organization's provider.

Incremental syncs

ParlanceKit keeps a snapshot of your source strings from the last sync. On the next run it compares against that snapshot and translates only what is new or changed. Strings you have not touched are left alone and are not billed again. Keys removed from the source are pruned from the targets.

The snapshot holds source strings only. It is overwritten on every run rather than accumulated into history, and it is deleted when you remove the repository, the configuration, or your account.

Reliability

Syncs run as background jobs. If a worker restarts mid-sync the job is requeued and retried, and billing is applied exactly once regardless of retries. Only one sync runs per repository at a time; pressing Sync while one is in flight returns the job already running.