Smartling’s GitHub Connector automatically delivers translations to GitHub once a Job is completed. This happens automatically in single branch mode or pull request mode, and manually when using on-demand mode. However, if you later make edits to the translations, the updates will not be automatically pushed to GitHub, as translation delivery is only triggered upon Job completion.
If you need to update translations in a Job that has already been completed, there are a few ways to have the updated translations delivered back to GitHub.
- Move content back in the workflow
- Manually export translations
- Create a scheduled translation export
Move content back in the workflow
If you need to make updates to completed translations and have them delivered back to GitHub, content must be moved back in the Smartling workflow to the In Progress state. Once the necessary edits have been made and submitted, the updated translations will be delivered to GitHub when the Job is completed again.
What You See In GitHub
If a completed Job goes back into the In Progress state before the translations are merged and the initial pull request is merged, then the connector will update just files that have been changed. This is seen only when the Job is re-completed. In this case, you will see a single file with multiple commits.
If the translation pull request with multiple languages has already been merged and then the Job is re-opened and only one or some languages worked on, for example:
Then, you may see that only the files that have changed are delivered in a new translation pull request.
Manually export translations
You can edit translations using any method documented in Options for Editing Translations. Once those edits are saved, the GitHub Connector will not automatically send the updates back to GitHub because the Job was already completed. However, you can manually send translations to GitHub by using the Export Translations button on the configuration set that contains the updated strings. For more information, see Manually Export Translations to GitHub.
Create a scheduled translation export
Creating a scheduled translation export allows you to automate translation synchronization on a defined schedule. This is especially useful if you rely on having the latest translations for tasks like creating nightly test builds or if your team frequently edits published translations. A scheduled export provides automated translation delivery outside of the regular connector flow. For more information, refer to GitHub Connector Scheduled Tasks.