The GitHub Connector automatically delivers translated files to the delivery branch in GitHub upon completing a translation Job in Smartling.
However, if you edit published translations in Smartling after the original translation Job is completed, those changes won't be automatically pushed to GitHub. In that case, you can manually send translations to GitHub anytime.
With this flexibility, you can ensure translations are in sync between Smartling and your GitHub repository, regardless of when you update them.
Note: The translation export process will not be instant and may take some time to generate.
How To Manually Export Translations
- Go to your GitHub Connector project in Smartling and click Settings
- In the GitHub Connector Settings, on any enabled configuration set, click Export Translation
-
Select a branch, files, target languages, and translation state (current or published).
- Current translations: The content in its current state in the workflow.
- Published translations: All published translations in the specified language for the specified file.
This feature is available in all configuration modes. This feature is essential to translation delivery when set to On Demand mode because translations are not exported automatically when using that mode.
Important Considerations
Re-exporting files
It's important to note that if you're trying to export a translated file that has been previously exported and GitHub is already in sync with Smartling, the translation export will be ignored by GitHub because there are no new changes to write to your repository.
Exporting the correct file version
It is common to have the same file in different branches in GitHub. Because they are in different branches, each file has a different namespace and, therefore, is unique in Smartling. This leads to multiple versions of the same file listed in the GitHub tab in your GitHub project in Smartling.
After you export a file, the "last modified" timestamp in Smartling is updated to the same time the file was exported. You can find the file versions in the Files tab to see if you have exported the correct file. The file with the same "last modified" timestamp as when it was exported is the file that was sent to GitHub.