Manual
Overview Getting Started Core concepts Quick Start Guide Create an account and sign in Projects Create and manage projects Project settings Languages Workflow and translation lock Translation Keys Key names and groups ICU messages and placeholders Translating The translation editor Keyboard shortcuts Machine translation Review & Reports Review workflow Reports Branches & Merging Branch workflows: create, merge, and delete The Branches page Tags Translation Memory How translation memory works Glossary The glossary Import & Export Import and export files File formats Integrations GitHub GitLab Slack, Mattermost and Microsoft Teams Repository and API keys Tags from Git tags Webhooks Teams & Access Roles and permissions Teams Inviting people Project access Account & Organization Account settings Organization settings Billing & Plans Plans and limits
CLI
Overview Installation Set up a project Configuration File formats Use the CLI in CI Commands ct push ct pull ct status ct translate ct check ct merge ct tag ct init ct snippet
API
Overview Introduction Authentication Languages and time zones Rate limiting Errors Endpoints Authentication routes Account Organisation Teams Projects Project languages Project members and teams Project webhooks Project API keys Branches Tags Keys Translations and review CLI and CI Translation memory Glossary GitHub GitLab Repository link Guides Pull translations for your build MCP server for AI agents
Log in Get started free
Commands

ct push

Send the source strings of a branch to Continuous Translations.

1 min read ยท Updated October 2026

Reads the source file and sends its strings to the project. New and changed strings are updated, and a changed string sends its translations back to draft. Other Git branches become Continuous Translations branches of the same name, created from main, see Which branch.

SH 
ct push
OptionEffect
--translationsAlso uploads the existing translation files (first import)
--pruneRemoves keys that left the file. The prune setting in ct.yml does this on every push
--dry-runOnly reports how many keys it would send

When it is done, ct push reports what changed:

TEXT 
Pushed 128 keys to main: 3 new, 2 changed, 1 removed, 122 unchanged.

Good to know #

  • push never overwrites existing translations, unless the project allows import overwrites.
  • Pushing twice changes nothing, so a pipeline that commits pulled files won’t loop.
  • Values that are not text are skipped with a warning.
  • With --translations, files are read for every language of the project that has one. Use it once to import what you already have.

Needs #

An API key with the keys:write scope, plus translations:write with --translations. See Push source strings for the route behind it.