Repository projects are the default setup for continuous app localization.
Who This Is For
Use repository projects when your team wants localization to run inside the same Git workflow used for app development.
This is usually the best fit when you:
- Keep iOS or Android localization files in source control.
- Want sync runs triggered from branch changes.
- Prefer reviewing localization changes through pull requests.
Setup Flow
- Connect GitHub, GitLab, or Bitbucket.
- Select repository and branch.
- Choose project preferences (tone, custom prompt, automation options).
- Start initial sync.
What Happens During Sync
A repository sync for app localization typically:
- Clones the selected branch.
- Detects supported localization files.
- Parses base and localized content.
- Queues missing or needs-review translations.
- Writes normalized output.
- Commits and opens or updates a pull request.
This gives you a repeatable path from source changes to review-ready localization updates.
Important Settings
- Auto Sync: Trigger sync from push webhooks.
- Auto Remove Stale Keys: Remove stale extracted keys.
- Auto Retranslate on Key Rename: Requeue translated rows when rename matching is detected.
Output
Repository projects can write changes, commit them on automation branches, and create pull requests for review.
Common Mistakes
- Connecting the wrong branch and expecting updates from another branch.
- Disabling Auto Sync and expecting push-triggered localization updates.
- Mixing large language rollouts with major base-copy changes in one run.
- Reviewing merged output without checking
NeedsReviewrows first.