2025-07-16 Merge docs translations upstream
Description
Single issue for pushing a batch of product docs translations upstream the week of 2025-xx-xx
Scope
- Create an "Update Production Translation MR" that will move translated documentation from the localization fork to the upstream production project
- Move content from our production fork's
main-translationbranch to the upstream project on a new branch titleddocs-i18n/upstream-batch-push-YYYY-MM-DD ❗ Split MRs into smaller MRs- Ensure pipelines pass, make and document necessary adjustments
- Follow the MR template established for this process
- Ensure all changes comply with the documented workflow: https://gitlab.com/gitlab-com/localization/docs-site-localization/-/blob/main/translation_mr_review_workflow.md?ref_type=heads#gitlab-maintainers-responsibilities-on-update-production-translation-mrt
- Drop notes on iterations to make for CI/CD in each project
Links to sources
| Project | Repository Links |
Forked prod |
Upstream translation MR | Latest GITTECHA MR included |
|---|---|---|---|---|
| GitLab | No upstream merge will happen due to high volume of errors in Phase 1 resend | |||
| Operator |
gitlab-com/localization/tech-docs-forked-projects/prod/gitlab-operator!24 (merged) |
|||
| Omnibus | ||||
| Runner | ||||
| Charts | ||||
| Docs |
Tasks to complete
-
Create upstream translation MRs and link them in the table above -
Document any CI/CD iterations made in relation to this translation push in the issue here -
All translation MRs merged upstream -
Follow up issues created for outstanding items
Edited by Rasam Hossain