You can add the above process to your CI/CD pipeline, but it’s even better to run it earlier:
Whenever a developer updated any text, simply run the command to keep translations up to date.
This keeps translations current, helps spot missing entries early (for example, during PR review), and is quick to set up.
For package scripts and CI jobs, see Curl Command Details for practical flags such as --fail-with-body, --silent --show-error, --compressed, and safe output-file handling.
If you use GitHub Actions, the official doloc GitHub Action can commit, check, or propose translation updates in CI.
For a more detailed discussion on when to run doloc, see our guide on When to Run doloc?.
Don’t want to run curl commands manually? Check out our IntelliJ plugin
for one-click translation of XLIFF and ARB files directly from your code editor.
Further Reading
File Format Guides – Supported file types and how to prepare/submit each for translation.
Integration Guides – Step-by-step setup for Angular, React Intl / FormatJS, Android, Flutter and more.
GitHub Actions – Commit, check, or propose translation updates with the official doloc action.
Options – How to pass configuration parameters to the translation endpoint.
Examples – Complete input/output samples for supported file formats.
When to Run doloc – Best practices on integrating doloc into your development cycle.
Curl Command Details – Recommended curl flags for scripts, CI, compression, and HTTP error handling.