Draft: Add new workflow and restructure system prompt accordinlgy

Description

Following these threads about new proposed translation workflow:...

  1. gitlab-com/marketing/digital-experience/about-gitlab-com!3813 (comment 3052138489)
  2. #19 (comment 3052366481)

...this MR adds a new Determine Translation Type section to the system prompt, in order to route between 2 workflows: one for translating only new yml files, and the other for more complex scenarios where existing translations need to be updated.

Type of Change

  • New feature == New dedicated workflow + routing logic in the system prompt + some cleanup of system prompt based on that
  • Bug fix
  • Documentation update
  • Style guide or terminology update
  • Configuration change
  • Other (please describe)

Related to Design separate "update translation" workflow d... (#19 - closed)

Testing

  • Tested locally
  • Verified with sample translations
  • Checked against style guides
  • 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)

Changelog Preview

## [Unreleased]
- Added new translation workflow and routing logic to system prompt
- Added placeholder folder and file with reference to the "Update Existing Translations" workflow
- Added guidance to "Never Translate" section to preserve existing values (e.g., formId: 3240), not just keys

Checklist

  • Code follows project style guidelines
  • Documentation has been updated (if applicable)
  • Changelog entry has been added
  • No breaking changes (or documented if intentional)
  • Commit messages follow conventional commit format
  • All CI/CD checks pass

Additional Notes


Note: Merge requests without a changelog entry will trigger a warning in CI/CD. Please add one before merging to main.

For detailed changelog guidelines, see .gitlab/RELEASE.md.

Edited by Oleksandr Pysaryuk

Merge request reports

Loading