Create CI/CD automation to track GDATP translation MRs in Argo for ABOUTAI

Problem

ABOUTAI translation requests require manual tracking when Translation MRs are created using GDATP (via GitLab UI or VS Code). Engineers or program managers manually add MR cards to Argo requests and complete workflow steps by hand.

Solution

Jack proposed an approach in https://gitlab.com/gitlab-com/localization/argo-gitlab-integration/-/issues/78#note_3006198798 where Translation MRs include a source MR reference in their description. A CI/CD check extracts that reference to look up the Argo request and add the Translation MR card, triggering the necessary step(s) in the Argo workflow.

Need to build CI checks in about-gitlab-com:

Job 1: when Translation MR is created

  1. Triggers on MR creation
  2. Extracts source MR number from Translation MR description
  3. Looks up corresponding Argo ABOUTAI request
  4. Adds Translation MR card to Argo request
  5. Completes the "Waiting for Translation MR" step via Argo API (per comment https://gitlab.com/gitlab-com/localization/argo-gitlab-integration/-/issues/78#note_3013005748
  6. Argo updates the asset status

Job 2: when Translation MR is merged

  1. Triggers on MR merge
  2. CI/CD completes the "Waiting for MR to Merge" step via Argo API
  3. Argo updates asset status and auto-closes the Request

Note: as long as there is only one component per request, this is straightforward. If we later support multiple components per request, this solution will need to be revisited (per @jcole-ext in #626 (comment 3039705746)).

Prerequisites:

Edited by Oleksandr Pysaryuk