Github_Lokalise_logos

GitHub integration for Lokalise

Use our Github integration in your localization process to keep your source files and translations synchronized – seamlessly. Integration with the Enterprise version is also available.

Try all features free for 14 days · No credit card required

How the Lokalise + GitHub integration works

  • Connect your tool with Lokalise using the integration
    Connect

    your repository with Lokalise

  • Push language files from your repository to Lokalise using the integration
    Push

    your language files

  • Translate strings using the Lokalise integration
    Translate

    all the new and updated strings

  • Pull translated strings to your repository using the Lokalise integration
    Pull

    translated strings back to the repo

Smooth localization of your source files

  • Auto-sync your files

    When you push your code to GitHub, it automatically detects all changes and adds new keys to Lokalise. Once the new keys are translated, you can create a pull request from Lokalise and merge the files to a selected branch on GitHub. Sync your files with a push of a few buttons and keep them up to date at all times.

  • Eliminate monkey work

    Imagine manually downloading and uploading files back and forth to GitHub and Lokalise. It's slow, inefficient, and is essentially wasting developer time doing monkey work. The GitHub integration automates and speeds up this process, and in the end, helps you significantly shorten the product release cycle.

  • Be organized and precise

    Avoid human errors by replacing manual code exports and imports with automated file exchange between GitHub and Lokalise. Use the Preview option when you create a pull request – it will allow you to see and confirm the resulting file/folder structure before pushing it to GitHub.

Who uses the Lokalise + Github integration?

An illustration representing Lokalise integrations
  • Developers

    The auto-pull option, as well as automatic key generation for new and updated text elements, eliminate a ton of manual work for developers.

  • Managers

    Streamline the workflow by asking developers to push their code to Lokalise every time they make any changes. All you'll have to do is assign tasks to translators.

  • Translators

    Translators won't have to wait on developers to excerpt texts from the code, define keys, and add them to Lokalise. That's all done with the push of a button.

Frequently asked questions

How to create a Pull Request (PR)?
Go to the Download Menu, select the relevant options, and trigger GitHub by ticking the GitHub checkbox. Then, make a Build. In this case, the PR will be created in your repo. If you have more than one repo linked to the project, select the appropriate one using the Filter repositories field.
I have updated strings in my GitHub file, but the values are not updating on Lokalise. What am I doing wrong?
Make sure that the ''Replace modified values'' option is enabled in the pull settings. You can read more about all the upload parameters in the Upload files article.
I'm trying to create a Pull Request (PR) and the structure of files in the created PR does not match the file structure in my repository.
To match the right structure of your files, you have to name files properly and select the right options when creating a PR. Please check the Filenames article for reference.

See Lokalise + Github in action

Get a live customized demo and let us show you how the Lokalise + Github integration can improve your localization workflow.

Book a demo