Features How It Works FAQ Integrations Blog Get Early Access
Back to Integrations
Triggers

Workflow Triggers

Triggers control when LocoLingua runs a translation job against your repository. Some triggers fire automatically in response to VCS events; others are initiated by hand from the portal. The table below lists every trigger, its current status, and which VCS providers support it.

Trigger Reference

Triggers marked Available are fully supported today. Triggers marked Coming Soon are on the roadmap and will be announced when released.

LocoLingua workflow triggers, their availability status, the VCS providers that support each trigger, and a short description of how each trigger works.
Trigger Status Supported VCS Hosts Description
Manual Available GitHub GitLab Run a translation job on demand from the LocoLingua portal. Translations are committed to a new branch and, optionally, a pull or merge request is opened against your default branch.
Pull Request / Merge Request Available GitHub GitLab Automatically trigger a translation run whenever a pull request (GitHub) or merge request (GitLab) is opened or updated against your default branch. Keeps locales in sync with every code change without manual intervention.
Scheduled (Cron) Coming Soon GitHub GitLab Bitbucket Run translation jobs on a defined schedule — for example, nightly or weekly — so locale files are always up to date without requiring a code event.
Push to Branch Coming Soon GitHub GitLab Bitbucket Trigger a translation run whenever a commit is pushed to a specified branch (e.g., main or release/*). Useful for teams that merge frequently and want translations generated continuously.

How Each Trigger Works

Step-by-step explanation of the sequence of events for each trigger type.

Manual

Available

Run a translation job on demand from the LocoLingua portal. Translations are committed to a new branch and, optionally, a pull or merge request is opened against your default branch.

Supported on: GitHubGitLab
  1. User initiates a translation run from the portal.
  2. LocoLingua clones the repository and extracts translatable strings.
  3. Translated locale files are committed to a new branch.
  4. A pull request (GitHub) or merge request (GitLab) is opened for review.

Pull Request / Merge Request

Available

Automatically trigger a translation run whenever a pull request (GitHub) or merge request (GitLab) is opened or updated against your default branch. Keeps locales in sync with every code change without manual intervention.

Supported on: GitHubGitLab
  1. A pull or merge request is opened or synchronized in your repository.
  2. The VCS provider sends a webhook event to LocoLingua.
  3. LocoLingua checks out the PR branch and extracts new or changed strings.
  4. Updated locale files are committed back to the same PR branch.

Scheduled (Cron)

Coming Soon

Run translation jobs on a defined schedule — for example, nightly or weekly — so locale files are always up to date without requiring a code event.

Supported on: GitHubGitLabBitbucket
  1. User configures a cron schedule in the LocoLingua portal.
  2. At the scheduled time, LocoLingua checks the default branch for untranslated strings.
  3. Translated locale files are committed and a pull or merge request is opened if changes exist.

Push to Branch

Coming Soon

Trigger a translation run whenever a commit is pushed to a specified branch (e.g., main or release/*). Useful for teams that merge frequently and want translations generated continuously.

Supported on: GitHubGitLabBitbucket
  1. A commit is pushed to a configured branch.
  2. The VCS provider sends a push webhook event to LocoLingua.
  3. LocoLingua extracts new strings and commits updated locale files to a translation branch.
  4. A pull or merge request is opened for review.

← Back to Integrations   ·   Join the waitlist