Localize Pipeline Bisq Network tooling

Open-source localization automation

Review translations like code.

Localize Pipeline watches changed source strings, translates Java .properties and JSON files, validates the result, and opens normal pull requests that maintainers can review, amend, and merge. The optional Guardian follows up on translation reviews.

Start with the CLI Use the GitHub Action Agent index

Agent entry points

Start with the map, then run checks.

Agents should read the repository index first, inspect the target profile, then use the CLI preflight commands before changing translations.

llms.txt Repository structure CLI commands Self-hosted Guardian

Production credits

Battle-tested by Bisq maintainers.

Localize Pipeline runs the scheduled localization workflow for Bisq 2 and Bisq Mobile. It is battle-tested in production, where generated translations land as ordinary GitHub pull requests for maintainer review. Bisq 2 is configured for 54 target locales; Bisq Mobile currently carries 13 mobile target locales, or 14 languages including English.

Bisq 2 54 target locales Bisq Mobile 13 mobile target locales, 14 languages including English

The review can improve the next run, too.

Guardian follows up on translation PRs: checked corrections for this review, proposed pipeline fixes for recurring problems.

It reads feedback from the human reviewers and bots you trust, including CodeRabbit. You choose which repositories it watches, what it may edit, and how much work it may start.

Guardian is optional and self-hosted. Your project runs it with its own credentials and Codex plan. It starts in observation mode; editing and PR creation require explicit configuration.

Set up Guardian

A review becomes a fix

  1. A reviewer flags a translation. Guardian checks it against the current source, glossary, and permitted edit scope.
  2. A valid correction gets a signed commit. A bot reply links the change. Alternatives, deferred work, and glossary decisions stay visible for human review.
  3. A recurring defect can get a pipeline PR. The proposed fix includes a before-and-after regression test and opens ready for review.

You still decide what to merge. Guardian never merges PRs or changes glossary policy on its own. Review follow-up on its pipeline-improvement PRs is not yet automated.

Choose the path

Adopt it without changing how maintainers review code.

01 Local project setup

Scaffold config, validate credentials, run smoke checks, and test dry runs.

 02 GitHub Action workflow

Translate changed strings from CI and open reviewable pull requests.

 03 Scheduled production service

Run Docker Compose plus cron for repositories backed by external sources.

 04 Self-hosted PR Guardian

Run an optional operator-owned review loop with explicit allowlists and your own model account.

Adoption flow

One onboarding PR, then normal translation PRs.

  1. 1

    Bootstrap

    Run localize bootstrap-pr to add config, glossary, workflow, and target-repo notes.

  2. 2

    Verify

    Keep dry-run mode on while localize doctor, localize smoke, and validation pass.

  3. 3

    Publish

    Enable writes, review the generated PR, and let translation memory improve future runs.

Formats and providers

Modular by contract, not by convention.

Java .properties and JSON are built in. Additional formats plug into the same adapter contract, so parsing, changed-key detection, placeholder validation, quality gates, and publishing stay reusable across projects.

Java .properties JSON AISuite GitHub PRs
Repository structure New format checklist Local runs Adding locales

Operational surface

Keep state visible and portable.

localize memory stats --memory-file logs/translation_memory.json localize memory export --memory-file logs/translation_memory.json --output shared-memory.json localize memory import --memory-file logs/translation_memory.json --input shared-memory.json localize memory suggest --source-text "Save change" --locale de --format-id json