feat(generation): first-class output-language support for generated docs#756
Merged
Conversation
Promote the config-only language setting (#99) to a first-class option: - `repowise init --language <code>` (15 languages), validated via the new dependency-free `generation.languages` leaf module - advanced interactive init asks for the output language (English default) and shows it in the config summary - the choice persists to `.repowise/config.yaml` (single-repo and workspace init) so `update` regenerates changed pages in the same language - honor the configured language in paths that silently defaulted to English: workspace `generate`, the server regenerate job, and the pipeline orchestrator fallback config; `PageGenerator` now falls back to `config.language` when the arg is omitted - docs: README one-liner, CLI reference, user guide, CONFIG.md, changelog
|
✅ Health: 7.7 (unchanged) 📋 At a glance
🩹 Review priority (files here with the most recent bug-fix history — defects cluster, so review these first)
🔎 More signals (2)🔥 Hotspots touched (5)
2 more
🔗 Hidden coupling (2 files)
📊 Full report · ⭐ Star Repowise · 📥 Install bot · Last updated 2026-07-10 14:38 UTC |
swati510
approved these changes
Jul 10, 2026
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.
What
Promotes the config-only wiki output-language setting (#99) to a first-class option.
repowise init --language <code>: choose from 15 languages (en, ru, es, fr, de, zh, ja, ko, it, pt, nl, pl, tr, ar, hi). Prose is generated in that language; code, file paths, and symbol names stay untranslated..repowise/config.yaml(single-repo and workspace init), sorepowise updateregenerates changed pages in the same language.workspace generate, the server regenerate job, and the pipeline orchestrator fallback config.PageGeneratoralso falls back toconfig.languagewhen the argument is omitted, so future callers cannot repeat that bug.generation/languages.py) so the CLI validates the flag at startup without importing the page-generator stack.Docs
README (one line in the Docs layer row), CLI reference, user guide, CONFIG.md, changelog. Changing the language later does not retranslate existing pages; re-run
init --force --language <code>.Testing
PageGeneratorpicks the language up fromGenerationConfigwhen the arg is omitted, and updated the advanced-config keys test.--language hi(openai / gpt-5.4-nano); generated pages come out in Hindi with code and symbol names untranslated, andlanguage: hilands inconfig.yaml.