The GitHub Connector automatically delivers translated files to the delivery branch in GitHub upon completion of the Job in Smartling.
However, if you need the translations before Job completion, or if you edit published translations in Smartling, you can send translations to GitHub manually, at any time.
With this flexibility, you can easily manage your translations and ensure that they are properly integrated into your GitHub repository.
Note: The translation delivery process will not be instant and will take some time.
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. The benefit of this when the configuration set is set to Pull Request or Single Branch mode is that you don't have to update source content needlessly to activate translation delivery. This feature is essential to translation delivery when set to On Demand mode.
It's important to note that if you're trying to export a translated file that has been previously exported and has no changes to source content, then Smartling cannot deliver the file to GitHub again. This is a GitHub limitation.
Exporting the right 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 filename 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 for the file in Smartling is updated to the same time the file was exported. To check that you have exported the correct file, locate the file versions in the GitHub tab. The file with the same "last modified" timestamp as when it was exported is the file that was sent to GitHub.