Skip to main content

Documentation Index

Fetch the complete documentation index at: https://support.lilt.com/llms.txt

Use this file to discover all available pages before exploring further.

LILT + GitHub connector enables companies to automatically push and pull content between GitHub and LILT. This saves you time by providing seamless localization while letting you continue to work in the systems you know.
  • Submission via GitHub: Creating or updating content in GitHub automatically creates a Job in LILT containing the source content that needs to be translated.
  • Translation Method: During configuration, the user can specify the desired workflow:
    1. Instant Translate: GitHub content is immediately localized into any desired language using LILT’s Contextual AI.
    2. Verified Translation: Send GitHub content to LILT’s in-house translators for localization.
  • Deliver to GitHub: When a LILT Job is finished, the localized content is automatically delivered to GitHub.

​
Configuration

During the process of onboarding a new client, LILT will help identify whether the GitHub integration can be used. If it can be used, LILT will set up the GitHub integration for the client.

​
Workflow

Once the connector is configured, content is automatically moved between LILT and GitHub as outlined in the sections below.

​
Project creation

LILT periodically checks for new content on GitHub. When new content is detected, LILT Projects are automatically created for the content to be translated.

​
Project completion

LILT periodically checks for completed LILT Projects. Completed Project content is automatically pushed back to GitHub into the folders specified during configuration.

​
Limitations

LILT does not continuously check for new content; it only periodically checks for new content and completed Projects. The frequency that LILT checks for content is determined when the connector is set up.

​
Pull Request (PR-only) workflow

The PR-only workflow is an optional GitHub connector mode designed for teams that manage content changes through pull requests. Instead of translating from a single fixed branch, the connector detects eligible pull requests and translates the content from each PR’s source branch, so translations can be reviewed and merged alongside the code/content changes.

How it works
  1. Find matching pull requests (Import)
    1. On import, the connector uses the GitHub API to look for pull requests that match your configured criteria (for example: PR labels, PR title, and/or approval status). Pull requests must all be from the same primary branch listed in the LILT Connectors admin page.
    2. If one or more PRs match, the connector selects the source branch for each PR.
  2. Extract and submit content for translation (Import)
    1. The connector clones the repository, checks out the PR’s source branch, and extracts files using your configured include/exclude patterns.
    2. The extracted content is then submitted to Lilt for translation.
  3. Notify contributors in GitHub
    1. The connector adds a label and/or comment on the pull request to indicate that content has been imported for translation (or to indicate there was no translatable content).
  4. Return translations to the same PR branch (Export)
    1. When translations are ready, the connector downloads the translated files and pushes them back to the same PR source branch, so the PR includes the translated updates before it’s merged.