Add argo_translation.yml for continuous translation process

Lauren Barkerrequested to merge
add-argo-translation-config into master

What does this MR do?

This MR adds the argo_translation.yml configuration file to enable our Japanese translation workflow for documentation.

Purpose:

  • Enables automated tracking of English content changes in the doc/ directory
  • Facilitates the translation process through our GitLab Argo Integration
  • Follows established pattern of placing translation configs at root (similar to crowdin.yml)
  • Part of comprehensive translation implementation across repositories (Runner, Operator, GitLab, and Omnibus)

Workflow:

  1. Argo tracks changes to doc/ directory from our production localization GitLab Chart fork
  2. When MRs merge, Argo detects changes via GitLab Argo Integration webhook fork and determines files for translation
  3. Translated files return to our fork with the gitlab-translation-service label. See them here.
  4. After review, translations merge to fork's main-translation branch
  5. Final translations delivered upstream to /doc-locale directory, which has been added to all projects

Configuration Details:

  • Source: English (en-us) → Target: Japanese (ja-jp)
  • Tracking: All Markdown in doc/ (excluding hidden directories)
  • Delivery: /doc-locale directory

This is the next step in establishing continuous translation of technical documentation across GitLab projects. Similar argo_translation.yml files will be added to Runner, Operator, GitLab, and Omnibus repositories.

For details, see GitLab Localization Documentation

References

Related issues

  1. Closes gitlab-com/localization/docs-site-localization#209 (closed)
  2. Child of gitlab-com/localization&14
  3. Related GitLab MR
  4. Relate Runner MR

Author checklist

For general guidance, please follow our Contributing guide.

Required

For anything in this list which will not be completed, please provide a reason in the MR discussion.

  • Merge Request Title and Description are up to date, accurate, and descriptive.
  • MR targeting the appropriate branch.
  • MR has a green pipeline.
  • Documentation created/updated.
  • Tests added/updated, and test plan for scenarios not covered by automated tests.
  • Equivalent MR/issue for omnibus-gitlab opened.

Reviewers checklist

Edited by Lauren Barker

Merge request reports