Skip to main content
All CollectionsIntegrations
How to set up GitLab integration?
How to set up GitLab integration?
Updated over a week ago

To connect the GitLab repository to Lingohub, users must generate API keys with the associated permissions. We have provided here a guide on where to create a token for the GitLab and how to connect it to the Lingohub platform.

Create a GitLab API key by following the next steps:

  1. Sign in to the GitLab account.

  2. Navigate to the repository you want to connect to Lingohub.

  3. Click "Setting" and choose "Access token."

  4. Click "Add new token".

  5. Provide the token's name. Select the expiration date (if you don't select the date, this token will expire in 365 days. By default, you can set up the token maximum for 365 days from the current date.)

  6. Select scopes. Provide the "api" scopes, like in the screenshot below. This means that Lingohub will have complete read/write access.

  7. Click "Create project access token."

  8. Copy the token from the "Access Tokens" page. Save it, as you won't be able to access it again.

How to connect GitLab to Lingohub?

  1. In the Lingohub application, go to "Workspace" – "Plugins and integrations," find the GitLab plugin in the list (or do a search), and click on "Manage."

  2. Enter the GitLab authentication name, repository URL and access token. Now you can use the GitLab authentication in your projects.

  3. Create a Lingohub project and select the platform (the file format you want to localize). Click on "Create."

    Note: Lingohub will synchronize only selected file formats. The following platforms don't support Git setup: Contentful, Figma, Storyblok, and Zendesk. Read how to connect other platforms in the integration section of our Help Center.

  4. Go to the newly created project and click "Plugins" to see the Git integration. Click on "Manage."

Read how to manage Git plugin in our help center.

Awesome! You have finished the article about GitLab integration. If you have any questions, please contact our team at [email protected].

Did this answer your question?