Restore API identifiers reverted by the locadex sync in #1394 - #1406
Open
Chadha93 wants to merge 1 commit into
Open
Restore API identifiers reverted by the locadex sync in #1394#1406Chadha93 wants to merge 1 commit into
Chadha93 wants to merge 1 commit into
Conversation
#1393 restored changeTracking, crawl.started and scrapedData in the Spanish, French and Portuguese pages, and added the CI check that keeps API identifiers in English. Hours later the automated translation sync in #1394 rewrote the same 14 pages from Locadex's translation memory, which still held seguimientoDeCambios, suiviDesModifications, rastreioDeMudanças, rastreo.iniciado and dadosRaspados, and merged with that check failing. Every pull request since has failed the check. This reverses the .mdx and pt-BR OpenAPI hunks of #1394 exactly, which brings the pages back to the #1393 state. scripts/check-locale-api-literals.sh passes again. The translation memory is unchanged by this commit, so the next Locadex sync will reintroduce the same strings unless the terms are pinned as do-not-translate in the General Translation dashboard or the affected strings are retranslated there. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why every PR is failing the "Locale literals" check
The
Keep API literals untranslatedstep has failed on every pull request since 2026-09-08. Timeline:9a8730a4) addedscripts/check-locale-api-literals.shand wired it into CI, and restored translated identifiers in the localized trees.5b710116) extended the check to prose and restored the remaining ones:changeTracking(translated asseguimientoDeCambios,suiviDesModifications,rastreioDeMudanças),crawl.started(rastreo.iniciado) and the sample variablescrapedData(dadosRaspados).d7054044,locadex-agent[bot], merged 07:26 the same day) was an automated translation sync. It rewrote exactly the 14 pages Keep API identifiers in English in localized prose #1393 had fixed, plus one pt-BR OpenAPI description, from Locadex's translation memory, which still held the translated identifiers. Its own "Locale literals" check was FAILURE and it merged anyway.Root cause: #1380 and #1393 edited the localized files directly but did not change what Locadex stores as the translation (neither touched
gt-lock.json, and the memory lives in the General Translation service). The next sync treated the manual edits as drift and restored its cached output.What this PR does
Reverses the
.mdxandpt-BR/api-reference/v1-openapi.jsonhunks of #1394 one-for-one, returning the 15 files to their #1393 state.sh scripts/check-locale-api-literals.shpasses locally on this branch.gt-lock.jsonis left untouched.The repo's
CLAUDE.mdsays not to edit localized files by hand; this PR does so deliberately because the check that is blocking every other PR guards exactly these files, and the previous fix was applied the same way.What still needs to happen outside this repo
This will be reverted again by the next Locadex sync unless one of these is done in the General Translation dashboard:
changeTracking,crawl.startedandscrapedData(and ideally every enum value and property name from the OpenAPI specs) as do-not-translate glossary terms, orIt is also worth making the "Locale literals and extraction-hostile markdown" check required so an automated sync cannot merge over it, since #1394 merged with it failing.
🤖 Generated with Claude Code