Skip to content

LT-22652: Automatically update strings in Crowdin - #1046

Open
papeh wants to merge 3 commits into
mainfrom
feature/auto-update-crowdin
Open

LT-22652: Automatically update strings in Crowdin#1046
papeh wants to merge 3 commits into
mainfrom
feature/auto-update-crowdin

Conversation

@papeh

@papeh papeh commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Update Crowdin source strings as soon as they are updated in FLEx. Doing so requires Crowdin access, and developers frequently forget.

FUTURE WORK: automate list export

CI-ready checklist

  • Commit messages follow .github/commit-guidelines.md (subject ≤ 72 chars, no trailing punctuation; if body present, blank line then ≤ 80-char lines).
  • Builds/tests pass locally (or I've run the CI-style build via Bash script or MSBuild).

This change is Reviewable

Update Crowdin source strings as soon as they are updated in FLEx.
Doing so requires Crowdin access, and developers frequently forget.

FUTURE WORK: automate list export
@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 33.10%. Comparing base (f713635) to head (2be0870).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1046   +/-   ##
=======================================
  Coverage   33.10%   33.10%           
=======================================
  Files        1201     1201           
  Lines      277959   277959           
  Branches    37130    37130           
=======================================
+ Hits        92018    92019    +1     
  Misses     158146   158146           
+ Partials    27795    27794    -1     

see 1 file with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@papeh
papeh marked this pull request as ready for review August 6, 2026 19:04
papeh added 2 commits August 6, 2026 14:48
and build Release (not that it matters, but it looks consistent)
In case strings diverge and we don't remember to remove the branch
from crowdin.json when creating a branch for a patch on stable.
This will prevent stable strings overwriting latest strings.

@jasonleenaylor jasonleenaylor left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jasonleenaylor reviewed 1 file and all commit messages, and made 1 comment.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on papeh).


.github/workflows/patch-installer-cd.yml line 119 at r1 (raw file):

          ref: ${{ github.event.inputs.lcm_ref || 'master' }}
          fetch-depth: 0
          path: 'Localizations/LCM'

In the workflow we decided to clone LCM into the Localizations folder (since that is the only reason we needed it) devin caught that the uploadUpdatesForTranslation task deletes that folder. Doing this before the build will make the localization build fail, it could be done at the end though.

@papeh

papeh commented Aug 7, 2026

Copy link
Copy Markdown
Contributor Author

I thought Devin was being silly. Silly me. Unfortunately, deleting the actual LCM repo at the beginning of CopyLcmResxFiles will also prevent these strings from being uploaded. The uploadUpdatesForTranslation and Localize targets expect a different directory structure in LCM, so we'll have to rename one. Renaming the destination of CopyLcmResxFiles would break our structure in Crowdin, so we have to move the repository. We could call it liblcm or lcmrepo.

We want to upload sources before the build so that, if any strings have breaking changes, the build still succeeds the first time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants