How to Sync Translation Files with GitLab

If your team hosts translation files in GitLab, the typical workflow involves cloning the repo, navigating to the locale directory, editing the JSON or YAML file in a text editor, committing, and pushing. That's a lot of steps for a one-line translation fix — and it's completely inaccessible to anyone who doesn't use Git.

Glot's GitLab integration eliminates this friction. Connect your GitLab account, browse your projects and branches, open any locale file in a visual editor, and push changes back — directly to the branch or via a merge request. The entire round-trip happens in the browser.

Connecting Your GitLab Account

The connection uses GitLab's OAuth flow. You authorize Glot to access your repositories — your password is never shared, and the resulting access token is encrypted at rest using AES-256-GCM.

1. Go to Integrations and click Connect on the GitLab card.
2. You'll be redirected to GitLab to authorize Glot. Approve the request.
3. Once redirected back, your GitLab account is connected. You'll see your username and avatar on the integration card.

You can disconnect at any time from the same page. Disconnecting deletes the stored token immediately.

Importing Translation Files from GitLab

Once connected, the Import from Cloud button in the editor toolbar includes GitLab as an option. Clicking it opens a project browser:

1. Search and select a project — All projects you have access to (owned, member, or organization) are listed. Use the search bar to filter by name.
2. Switch branches — The default branch is pre-selected, but you can switch to any branch from the dropdown.
3. Navigate the file tree — Browse directories to find your locale files. JSON, YAML, ARB, and CSV files are highlighted and importable.
4. Click to import — The file is loaded into the editor. Its GitLab origin (project, branch, path) is tracked, so you can push changes back later.

Pushing Changes Back to GitLab

After editing, the Push to GitLab button appears in the toolbar. Clicking it opens the commit dialog with two options:

Direct Commit

Write a commit message and push directly to the branch you imported from. This is the fastest option for small fixes — a typo correction, an added translation key, or updating a value.

New Branch + Merge Request

For production branches, the safer workflow is to create a new branch and open a merge request:

1. Toggle to New Branch + MR mode in the commit dialog.
2. Glot generates a branch name (e.g. glot/update-1710720000000) which you can customize.
3. Write your commit message and MR title. Optionally include a description.
4. Click Push — Glot creates the branch, commits the file, and opens a merge request on GitLab. A link to the MR appears in the success message.

This means a translator, content manager, or product owner can propose translation changes through GitLab's merge request review flow — without ever using Git commands.

GitLab vs. GitHub: What's Different?

The GitLab integration follows the same pattern as the GitHub integration, with terminology adjusted for GitLab's model:

• Projects instead of repositories — GitLab uses project IDs internally, so the browser fetches by project rather than owner/repo.
• Merge Requests instead of pull requests — When you choose the branch + MR workflow, Glot creates a GitLab Merge Request instead of a GitHub Pull Request.
• Same editor, same formats — The import and editing experience is identical regardless of which provider the file came from.

Who Benefits?

• Teams on GitLab — Many organizations use GitLab (self-hosted or gitlab.com) as their primary VCS. Now translation files in those repos are directly accessible from Glot.
• Translators without Git access — Non-technical team members can browse, edit, and submit translation changes through the browser. Merge request review ensures quality control.
• Multi-platform teams — If your organization uses both GitHub and GitLab, you can connect both and switch between them from the same import dropdown.
• Open-source maintainers — Accept translation contributions without onboarding contributors to your Git workflow.

Security

All cloud connections use OAuth — Glot never sees your GitLab password. Access tokens are encrypted with AES-256-GCM before storage and decrypted only when making API calls on your behalf. You can revoke access at any time from both Glot's integration page and GitLab's application settings.

Get Started

Connect your GitLab account from the Integrations page, then open the editor and click Import from Cloud to browse your projects. Edit, translate, and push — all from one place.

Translation management shouldn't require command-line proficiency. With GitLab integration, Glot brings the full edit-commit-MR cycle into the browser, making it accessible to your entire team.