morningman opened a new pull request, #4331: URL: https://github.com/apache/doris-website/pull/4331
Generated translation PRs currently have no locale label, and normal generation defaults to two target pages. Add `translate-<locale>` (`translate-ja` for Japanese) and raise the normal default to at most ten target pages. Live `validate` remains limited to one exact source page; the planner still considers up to twenty tasks. Build Check now installs dependencies and runs unit tests before the translation gate, then builds the selected website scope and verifies static pages. The gate reads native source metadata and state, so it can reject invalid translations before a site build. Keep its full-scope environment separate from the build's version and locale filters. Validation: - Node 20.20.2: all 106 i18n tests pass. The new regression supplies eleven eligible pages and verifies that only ten targets/state records are written. - Both workflow files parse; the normal/validation limits and dependency-test-gate-build-static ordering are checked. - A fresh checkout of the real machine candidate PR is running the gate with no site build or build directory. - The local publication simulation will verify that the actual PR command carries `translate-ja` before this PR leaves draft. The label already exists in this repository. There are no new token permissions, automatic-generation switches, source edits or translation-state changes in this PR. ## Versions - [x] dev - [x] 4.x - [ ] 3.x - [ ] 2.1 or older (not covered by version/language sync gate) The managed translation scope stays Dev, 4.x and community. No documentation routes or navigation change. ## Languages - [ ] Chinese - [x] English Only the tooling README changes; there are no localized product-doc counterparts. ## Docs Checklist - [x] Checked by AI - [x] Test Cases Built - [x] Updated required version and language counterparts, or explained why not - [x] If only one language changed, confirmed whether source/translation counterparts need sync -- 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]
