What triggers a job
Pushes to watched branches. In Project → Settings → Repository → Watched branches, pick the branches whose new or changed source strings should be translated automatically. Usually that is main, but you can watch several. A push with string changes starts a job; a push without any doesn't.
Pull requests (optional). Turn on Translate pull requests and new strings in a PR are translated and committed straight onto the PR branch, so the translations ship with the feature. Skip draft pull requests leaves drafts alone until they're marked ready.
Manual jobs. From the project dashboard, run a translation job on any branch and choose whether to open a pull request or push the translations directly.
What the pull request looks like
One PR per job, containing only your locale files, with only the keys that are new or changed in this job. Existing translations you have reviewed are left untouched. Nothing is pushed to your default branch without a PR unless you chose direct push on a manual job.
Reviewing before merge
Review the PR as you would any other. Change a translation in the diff if you disagree with it — your edit becomes the approved version and feeds the translation memory (see Translation quality). Merge when you're happy. Job status in the app moves through pending → processing → review → completed; a failed job shows its error and can be retried.
Notifications and limits
Project → Settings → Notifications: a webhook URL and/or email recipients for job completed, job failed, QA issues and delivery failed.
Project → Settings → Budget: an optional monthly spending limit in EUR. Jobs are rejected, not silently run, once the limit is reached.
Git hosts
GitHub and GitLab are supported: connect the repository, and pushes to watched branches open pull requests (GitHub) or merge requests (GitLab) the same way. Azure DevOps is on the roadmap — tell us at support@globalize.now if you need it and we'll let you know when it lands.