Added merge request templates for Translation MRs
What does this MR do and why?
We are currently working on removing the current dependency on using a fork based architecture (here's our Production fork for docs). Once translation is completed, for the inbound, we use GitLab-Argo Bot (with Developer role) that would automatically create Translation Merge Requests back to the docs repository. Here's all the Translation MRs that has been created for the forked docs project. As a part of this process we're currently adding couple of Merge Request templates that will be used by the GitLab-Argo Bot while building those Translation Merge Requests.
Related
Screenshots, screen recordings, or links to review app
N/A
How to set up and validate locally
No local verification required. Once merged, testing will be completed using Argo round-trips similar to this.
Merge request acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
- I have evaluated the MR acceptance checklist for this merge request.
-
If this MR changes how markdown is interpreted, share this MR in the
#tech-docs-localizationslack channel. The translation tooling might need to be updated, for example if new syntax is added or existing syntax rendering is changed.