LingoHub offers dedicated synchronization controls to keep your project structure aligned whenever files or languages are removed in your source system. Because repositories and content management systems handle assets differently, LingoHub separates these behaviors into two distinct settings: Delete removed containers (for Git repositories) and Delete removed languages (for CMS integrations).
1. Delete removed containers for Git integrations
This setting applies to Git-based projects, including GitHub, GitLab, Bitbucket, and Azure DevOps.
Behavior & segment handling
When files are deleted: When enabled, running a Git pull removes resource files from LingoHub that no longer exist in the repository.
Pull conditions for deletion: Deletions only occur when pulling all files, and exclusively on the specific branch configured for the project in LingoHub. LingoHub will not delete files if you pull only a subset of files or synchronize from a different branch.
Safety for segment translations: Deleting a container does not permanently erase your language settings or translation history. Instead, the associated segment translations will be deactivated. If the file is reintroduced to the repository later, these segments and their history can be reactivated.
Default states
New Git projects: Enabled by default.
Existing Git projects: Disabled by default to preserve established workflows. Workspace members can enable it manually at any time.
How to configure
Open your Git project and navigate to Settings.
Select the Integration (GitHub / GitLab / Bitbucket / Azure) tab.
Under Branches & Files, toggle Delete removed containers on or off.
2. Delete removed languages for CMS integrations
For CMS and marketing platforms, such as Zendesk, Contentful, Storyblok, Stripo, and HubSpot, LingoHub manages obsolete languages using Delete removed languages.
Behavior & segment handling
Permanent deletion: When enabled, any target language no longer returned by the CMS during synchronization is deleted from LingoHub, along with all of its segment translations.
Source language protection: The project's source language is never deleted, even if the source system stops reporting it.
Execution trigger: Target language deletions are executed when updating the structure in a synchronization run. Running a standard text-only import will not delete languages.
Platform defaults & recommendations
Platform | Default (New projects) | Default (Existing projects) | Recommendation & Strategy |
Zendesk, Contentful, Storyblok | Enabled | Disabled | Keep enabled. Languages on these platforms are managed globally in the CMS and synchronize seamlessly with LingoHub. |
Stripo & HubSpot | Disabled | Disabled | Keep disabled. Languages are managed inside LingoHub and not globally in the platform.* |
*⚠️ Additional considerations for Stripo:
Because target languages are added and managed exclusively in LingoHub, they do not exist in Stripo until your first push. If Delete removed languages is enabled, a sync or structure update will treat these missing target languages in Stripo as removed and immediately erase them and all completed translations from LingoHub.
How to configure
Open your integration project and go to Settings.
Select your platform's tab under Settings (e.g., Integration (Zendesk)).
Under Integration settings, toggle Delete removed languages on or off.
To apply structural updates and process language removals, open the synchronization widget in your project header (e.g., Zendesk sync > Synchronize from Zendesk) and click Update structure.
Need more help?
Couldn't find what you were looking for? Reach out to our team at [email protected], and we will gladly assist you.