Repository navigation
docs(i18n): restore the issue-reference literals in the Uzbek QUALITY_GATES mirror - #17148
Merged
Merged
Conversation
Contributor
CI Coverage Report
Coverage artifact was not available for this run. |
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
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.
Summary
Wave 1018 (#17142) re-translated
docs/architecture/QUALITY_GATES.mdinto the 66 locales. In theUzbek mirror the translator rendered the two issue references in the
check:cyclesrow as№15281and№15159instead of#15281and#15159(the pre-wave mirror had both literalsintact).
tests/unit/cycle-docs-mirror-contract.test.tspins#15281in every published locale,so the unit shard that carries it went red on the base tip
3a99284445:This PR restores both literals in that one row and re-adopts the mirror's
target_hashin.i18n-state.json(only that entry changes; everysource_hashis untouched, so the documentkeeps showing up as
source-changedexactly as it does on the tip).A scan of every document the wave touched (13 sources × 66 locales) for issue references present
in the English source and in the pre-wave mirror but missing after the wave found exactly this one
pair (
uz/QUALITY_GATES.md). The other mirrors that lack a reference already lacked it beforethe wave (README
#13399in es/ko/pt/pt-BR, QUALITY_GATES#12149/#12502/#12530in gu/ja/ko,RESILIENCE_GUIDE
#12743everywhere — that document is still in drift on the tip).Validation
node --import tsx/esm --test tests/unit/cycle-docs-mirror-contract.test.tsnode scripts/i18n/check-translation-drift.mjssource-changedsources, ENVIRONMENT 66[loc], RESILIENCE_GUIDE 42[loc], no new entrygit diff --numstatdocs/i18n/uz/docs/architecture/QUALITY_GATES.md1/1,.i18n-state.json1/1Files:
docs/i18n/uz/docs/architecture/QUALITY_GATES.md,.i18n-state.json.The other deterministic unit reds on the tip are not touched here:
vision-key-scope-locales(GUARDRAILS mirrors, being synced on
docs/15306-provenance-20261019-044043),cli-env-quality-docs-mirrors(ENVIRONMENT after #16087) andresilience-pre-dispatch-docs-mirrors(RESILIENCE_GUIDE, 42 locales left) need a re-translationpass and are tracked in #15306.