Weblate Component Aliases: Share Translations, Keep Repositories Separate
Share translations across Weblate components while keeping repositories, access control, and quality checks separate.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Share translations across Weblate components while keeping repositories, access control, and quality checks separate.
Enable the push toggle in Weblate to automatically send committed translations to your remote Git repository. Learn how it targets the default branch, what credentials it needs, and how to verify pushes without overwriting upstream work.
Implement Weblate’s pull‑request workflow by configuring Git integration, securing tokens, and handling failures. This guide covers requirements, minimal design, trust boundaries, operational checks, and scaling considerations for single‑tenant deployments.
Weblate Projects group work, Components isolate it. Using per-component repository, filemask and workflow settings lets you manage JSON, PO and other formats in one project without forcing a single review policy.
Learn how to enable Weblate's auto-addon to scan a repository and create translation components automatically, with steps, verification checks, and rollback options.