Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,763
    • Issues 44,763
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,331
    • Merge requests 1,331
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #23256
Closed
Open
Issue created Jul 13, 2018 by Bob Van Landuyt@reprazentMaintainer

Communicate invalid translations back to Crowdin

Problem

Currently, when we notice invalid translations in linting, this is not communicated back to Crowdin.

Someone needs to manually disapprove the problematic translations in Crowdin in order to merge the rest of the translations, since all languages are in the same merge request (https://gitlab.com/gitlab-org/gitlab-ce/issues/43744).

Goal

  1. Create a mechanism to disapprove all translations that fail the linter
  2. Notify the groupimport team of what has been disapproved by the tool
  3. Update the docs (https://docs.gitlab.com/ee/development/i18n/translation.html) to reflect what we lint for, and with an example of what happens when something is automatically disapproved.

Notes

The intention is that this will be part of a larger automated pipeline which can be run on the master-i18n branch.

Some investigation was done into this here: #227181 (comment 410472981)

The solution for this issue should result in a script or something that can be run later in a CI pipeline. On completion of this issue, we should be able to manually run this in a local environment, with the intention of it being automatically triggered in a follow up issue.

There is an API on Crowdin that will allow us to change the approval status of a given string: https://support.crowdin.com/api/v2/#tag/String-Translations

Edited Sep 16, 2020 by Josianne Hyson
Assignee
Assign to
Time tracking