Repository navigation
docs(i18n): machine Russian translation candidates - #4427
Merged
Merged
Conversation
This branch was successfully deployed
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.
Russian translation candidate
Source commit:
7426acd4834f573b9c06e1161d7fa97ecb2a345fModel:
gpt-6-sol; glossary:1Review status: machine. Russian proofreading and the normal PR checks are still required.
community/how-to-contribute/how-to-share-blogs.mdf097fb1b367dFailed or skipped tasks
None.
Candidates retained with warnings
None.
Validation
Updates at or below 30% translate only changed Markdown/MDX blocks and preserve other target blocks.
Change size is the sum of max(removed, added) non-empty English lines per diff hunk, divided by the larger old/new line count.
New documents, larger updates, glossary changes or baselines that cannot be aligned use full translation.
Generation uses at most three attempts per document. Deletions and code-only updates may need no model call.
Each retry receives the earlier validation errors. Third-attempt content issues are retained as warnings above.
Full attempt history and diagnostics are in generation.json and the page state records.
Committed source hashes, managed paths and target/state hashes are checked before applying candidates.
Master is checked before each model call and before publishing: unrelated merges are allowed, a page changed on master is dropped, and a translation configuration or tooling change discards the batch.
The publisher runs the shared PR translation-state, syntax and internal-link checks before pushing.
The normal PR build and human proofreading are still required before merging.
Shared PR admission checks: passed (translation state, syntax, internal links).