- Merging translations
- Recreate the merge request
- Recreate the GitLab integration in CrowdIn
CrowdIn automatically syncs the
gitlab.pot file with the CrowdIn service, presenting
newly added externalized strings to the community of translators.
GitLab CrowdIn Bot also creates merge requests
to take newly approved translation submissions and merge them into the
files. Check the merge requests created by
to see new and merged merge requests.
By default CrowdIn commits translations with
[skip ci] in the commit
message. This is done to avoid a bunch of pipelines being run. Before
merging translations, make sure to trigger a pipeline to validate
translations, we have static analysis validating things CrowdIn
doesn’t do. Create a new pipeline at
(need Developer access permissions) for the
If there are validation errors, the easiest solution is to disapprove the offending string in CrowdIn, leaving a comment with what is required to fix the offense. There is an issue suggesting to automate this process. Disapproving excludes the invalid translation, the merge request is then updated within a few minutes.
If the translation has failed validation due to angle brackets
it should be disapproved on CrowdIn as our strings should be
using variables for HTML instead.
It might be handy to pause the integration on the CrowdIn side for a
little while so translations don’t keep coming. This can be done by
Pause sync on the CrowdIn integration settings
After all translations are determined to be appropriate and the pipelines pass,
you can merge the translations into the default branch. When merging translations,
be sure to select the Remove source branch check box, which causes CrowdIn
to recreate the
master-i18n from the default branch after merging the new
We are discussing automating this entire process.
CrowdIn creates a new merge request as soon as the old one is closed
or merged. But it does not recreate the
master-i18n branch every
time. To force CrowdIn to recreate the branch, close any open merge
and delete the
This might be needed when the merge request contains failures that have been fixed on the default branch.
If for some reason the GitLab integration in CrowdIn doesn’t exist, you can recreate it with the following steps:
- Sign in to GitLab as
gitlab-crowdin-bot. (If you’re a GitLab Team Member, find credentials in the GitLab shared 1Password account.)
- Sign in to CrowdIn with the GitLab integration.
- Go to Settings > Integrations > GitLab > Set Up Integration.
- Select the
Select Branches for Translation, select
- Ensure the
Service Branch Nameis