Skip to main content
Content sync moves files between a connected source and a native project. GitHub is the executable content-sync provider currently supported. Other provider choices may appear in setup, but their content movers are not available yet. Connecting GitHub gives Platform access to repositories. It does not start a file sync or generate translations.

​
Configure content sync

  1. Connect GitHub and enable the intended repository.
  2. Open the project’s Automations page.
  3. Select Add content sync.
  4. Choose the GitHub resource and the source/project folders.
  5. Review the mapping and enable Sync content.
  6. Inspect the run and confirm the source paths in Files.
Pull brings source content into the project folder. Push sends translations that are already ready back to GitHub through a pull request. Review that pull request before merging it.

​
Connect the translation step

Content sync itself does not create translation jobs. Add a Source upload automation or request a translation after the source arrives. Review the translations before the next outbound sync. Use a small test file to verify the full sequence: source arrives, translation runs, review completes, and the expected target path appears in a pull request.

​
Avoid duplicate delivery

Decide whether Platform content sync or your CLI/CI workflow owns a given source-to-target mapping. Running both for the same paths can produce competing updates. Keep the repository branch and locale paths consistent across the chosen workflow. For troubleshooting, distinguish connection access, sync errors, generation errors, and review readiness. See Automation troubleshooting and the GitHub workflow tutorial.