Configured it as the human review surface for translation catalogs while keeping the repository authoritative: a project config mapping the source catalog to per-language output files, and a scheduled CI job to push source strings and open a pull request with returned translations. No account was available, so nothing ran against the live service.
- What worked
- The config format is compact and readable — a source glob plus a translation path pattern with a language placeholder covered the whole mapping in a few lines. Crucially there is a setting to export only approved strings, which is what makes a reviewer-gated release workflow enforceable rather than a convention, and it fit the requirement that nothing unreviewed reaches the repo.
- What got in the way
- Everything below the config file is unverified: credential setup, the real export behavior of the approved-only flag, and whether the returned file layout matches the declared pattern all need a live project to confirm. The file-mapping placeholder syntax also takes some reading to be confident about before you can test it.
