Remove MR creation process from core style guide

Oleksandr Pysaryukrequested to merge
opysaryuk-main-patch-df48 into main

Description

This content is fully covered by the system prompt's step 5 ("Create merge request"), added in Add merge request creation step to GDATP system... (!49 - merged). Removing to eliminate redundancy per Restructure core style guide to remove redundan... (#20 - closed).

Overlap analysis of all 7 points in the core style guide's "MR Creation Process" section that's being removed in this MR:

  1. "Identify source file path" is already handled by step 2 (locale extraction) in system prompt. Removing.
  2. "Create corresponding path in target locale" is already implicit in directory mapping and step 2. Removing.
  3. "Maintain identical file structure and naming" is already implicit in the translation workflow. Removing.
  4. "Include source reference in commit message" is not in system prompt, but not needed either: source MR is captured in the MR description template fields, and the agent already writes descriptive commit messages. Removing.
  5. "Use descriptive MR title" is already covered by the explicit [GDATP] title format in step 5. Removing.
  6. "Assign MR to person using agent" is already the last line of step 5. Removing.
  7. "Document translation metadata in MR description" is partially covered by the MR template fields that capture tool and source MR. The extra metadata the core style guide mentions (specific prompts given, translation decisions) is not in the template, but is also not needed. Removing.

No changes to system prompt needed , all essential guidance is already there. https://gitlab.com/gitlab-com/localization/gitlab-duo-agent-translation-platform/-/blob/main/system-prompt.md#5-create-merge-request

Related

Type of Change

  • New feature
  • Bug fix
  • Documentation update
  • Style guide or terminology update
  • Configuration change
  • Other (please describe)

Changelog Entry

  • Changelog entry added to CHANGELOG.md
  • Entry is in the [Unreleased] section
  • Used appropriate category (Added/Changed/Fixed/Deprecated/Removed/Security)
  • Included MR reference at the end of the entry (e.g., (!123))
Edited by Oleksandr Pysaryuk

Merge request reports