morningman opened a new pull request, #4545: URL: https://github.com/apache/doris-website/pull/4545
A developer currently cannot publish a correction to a Japanese, Korean or Russian document by editing its body alone: the old target hash produces target_modified, and adopting ownership: human permanently stops later automatic source updates. Make the existing automation ledger internal and let corresponding English/Chinese source revisions determine regeneration. With source inputs unchanged, a body-only PR now passes admission, renders the corrected translation and remains outside model selection. Git derives the acknowledged source pair from the target's own content-changing commit; no shard edit, hash calculation, legacy migration or ownership flag is required. A later change to either corresponding source permits regeneration. English remains authoritative for technical facts, with Chinese supplied as supplementary context; a Chinese-only change forces refresh instead of reusing every unchanged English block. Automatic generation records both source fingerprints normally. Existing ledgers are read without a mass metadata migration, and registered manually created translations can start without a ledger. Keep open-PR reservations and target/state race guards. Include Chinese counterparts in generation/publication drift checks and reject uncommitted source inputs. Dev/4.x can share a new result only when their Chinese references also match. Preserve historical blog exclusion, English/Chinese-only legacy versions and paused groups. Mark repository edits separately from complete human proofreading and replace the old manual-state instructions with the body-only contributor workflow. Validation: - 413 Node checks: 411 passed, 2 conditional skips; 27 workflow/security checks passed. Offline configuration validation and all-locale source-history validation passed. - Real isolated five-language fixture: the contributor commit changes exactly three translation bodies and zero ledger files; normal translation admission, SSR, canonical/indexing, manual provenance and Chromium hydration pass. Updating the Chinese counterpart subsequently makes all three translations eligible for regeneration. - Real-Git regression cases cover JA/KO/RU body-only edits, unchanged/unrelated sources, English-only and Chinese-only updates, formerly human-owned records, missing initial ledgers, concurrent target/source edits, protected SQL/numerical facts, forced-plan rejection and Dev/4.x reference isolation. - Read all real records without errors: JA 3,296, KO 3,389, RU 3,380; effective source snapshots use cached Git trees rather than one subprocess per normal page. Only small isolated fixtures were built locally. | Repository review checkpoint | Conclusion | | --- | --- | | Goal | Developers submit only translated prose; matching source-pair changes control regeneration. | | Focus | Reuses existing native adapters, state readers, planner and guarded writer; no state-adoption workflow or extra bot metadata commits. | | Information architecture | Existing versions, plugins, scope exceptions and blog history policy remain authoritative. | | URLs / anchors / navigation | No moves, slugs or navigation changes; native metadata, technical-content and heading checks remain enforced. | | Frontend / mobile / SSR / themes | Adds a localized manual-edit notice through the existing five-language message map; no styling/layout/theme-token changes. | | Validation | Existing checks plus real Git, normal admission and five-language SSR/browser fixtures cover the contributor workflow. | | Other correctness / maintenance | Retains race protection, source provenance and honest review identity; no new permissions, secrets or dependencies. | Self-review found no remaining blocking issue. Normal PR checks must pass on the final head before merge. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
