Merge latest Crowdin translation PR to production (Weekly)

[linear]

Overview

This is a recurring weekly task to merge Crowdin translation PRs into production. The Production Engineering team is responsible for merging this, ensuring translations are regularly updated in production.

Frequency: Weekly (Friday)
Priority: Medium

Resources

• Crowdin GitHub Integration
• Translations Implementation Guide

Process

Scenario 1: PR Already Exists

• Check for open chore: new crowdin translations PR

• If PR exists:
  • Click "Update branch"
    • Edge case: resolve merge conflicts if they appear
  • Get the PR reviewed
    • Self review and approve if no manual changes have been made
    • If you had to manually make changes to the PR, request a review from another developer (any team member can approve)
  • Once approved, merge the PR to production
  • Mark this ticket as done

Scenario 2: No PR Exists

• Check for open chore: new crowdin translations PR
• If no PR exists:

  • Navigate to Crowdin GitHub Integration

  • Click "Sync now" to trigger translation sync

    

  • Wait 10 minutes for Crowdin to process and create the PR

  • Re-check the PR search link

  • If PR appears:

    • Follow Scenario 1 steps (update branch, get review, merge)

  • If no PR appears after 10 minutes:

    • Add a comment to this ticket: "No Crowdin PR this week (no new translations or sync produced no changes)"
    • Mark this ticket as done

Notes

• Crowdin automatically creates PRs with translations regardless of whether they've been reviewed by translators
• This ensures continuous deployment; manual review of translations can be done post-deployment if needed
• Only one chore: new crowdin translations PR should exist at a time

Future Stretch Goal

• Create a cursor script which gets gemini to check over the crowdin branch and reviews the new translations, providing suggestions for the developer to change if there are bad translations: ENG-3565

[linear]

ENG-3592