With the GitHub Connector, it’s possible to one or more of your GitHub content repositories to Locale for easy localization (l10n) and internationalization (i18n). While we advise caution when connecting more than one repository, for security and simplicity for translation content, it’s absolutely possible and in some workflows it’s even necessary.

After a content repository has been linked via the GitHub connector (example: main) and the languages have been set in a Locale project, this is where the magic happens. Locale will constantly be on the lookout for any changes or additions of content to your repository, and ensure they are processed according to the rules and setup for the project setup.

By applying an “auto-update” option to the project status, Locale will continuously check the status of your internationalization files and ensure they’re always up to date.

Once the translations have been processed, a pull request for the newly translated content is executed and ensures the delivery to your content repository. At your convenience or as necessary, a merge process can then be completed.

For more information on getting started, check out the articles on Adding the GitHub Connector to your workspace and Creating a GitHub project for translation in Locale
​
A small note: In rare cases, Github may fail to send the notification when a new commit is pushed on the branch we monitor for translation. This means a manual push for translation is required, or an additional commit on the branch will trigger the push of content for both commits.