Review workflow

The review workflow is how a human keeps final say over what ships, when needed. Team members view and adjust translations in the Localhero.ai dashboard, without touching code or git or filing a ticket, and their edits go back to the pull request as a commit.

You can also take AI out of the loop for some languages and use the same UI to fill in those translations manually when a new feature lands.

Reviewing AI translations

From the reviewer's side, the loop runs on the pull request:

  1. A developer opens a pull request that adds or changes keys in the source locale. The GitHub Action translates the keys that are new or missing and commits the result to that PR.
  2. Anyone with access to the project assigns one or more reviewers to the PR. Each reviewer gets an email pointing at it.
  3. The reviewer views the translations, rather than a code diff, and edits whatever needs fixing. Edits are saved on Localhero.ai.
  4. When done, the reviewer marks the PR approved, with a comment if they have one. The PR page shows how many of the assigned reviewers have approved, and shows "Ready to merge" when everyone has.
  5. If there were any edits to the translations, just click Sync to GitHub to push the edits back to the PR, so they are ready when merged.

You can also edit translations straight from the translations page, without a PR in context. Select the keys you changed, click Export to GitHub in the top right, and Localhero.ai opens a pull request with them, so the change goes through the same review and merge as any other PR.

Both features need the GitHub App installed. The App is what has permission to write to your repository. Without it, you can still review and edit in the dashboard, but nothing gets pushed back from there, and you would pull the translations down with the CLI instead.

Adding reviewers

Access to the project on Localhero.ai is all a reviewer needs. Invite them through the Members tab in your organization settings. No git, no code editor.

Developers keep the flow they already have. The locale files stay the source of truth in the repository, keys are added there, and translations arrive as commits on the pull request. Nobody has to switch tools to accommodate the other side.

Translating some languages yourself

Each target language in your project settings has an Auto-translate toggle. Turn it off for a language and Localhero.ai writes nothing for it: the Action and the CLI leave it alone and report it as skipped, while the language stays in the dashboard for your own translator to fill in.

Useful when some copy is authored rather than translated, marketing with its own argument in each market, legally sensitive wording, or a variant with special requirements.

Further reading: GitHub App for what the App can write to your repository, and translation quality at scale for how consistency holds up across many keys.

Last updated

Redo att testa?

Kom igång på några minuter. Inget kreditkort behövs.

Testa gratis Se priser