Why is my repository sync not running?
Work through the checks that explain a push that produced no strings, no translations or no pull request.
Start with what transglot recorded. For GitHub, open the GitHub App page from Integrations and read Recent deliveries. For GitLab, Bitbucket and Azure Repos, read the last sync panel on the host's card on the Integrations page. If a run is listed, its status and sentence usually name the cause. If nothing is listed, transglot never acted on the push: work through the checks below in order.
Was the push to the default branch?
Only pushes to the repository's default branch start a sync. A push to a feature branch, or a merge or pull request that is still open, does nothing until it lands on the default branch.
Did the push change the source locale file?
transglot reacts only when the push changes the file at your Source path for your Source locale. With a source path of locales/{locale}.json and source locale en, that is locales/en.json. A push that changes only target locale files, or files elsewhere, does nothing.
Is the repository linked to a project?
Installing the GitHub App or adding a webhook is only half of it. The repository must also appear in the list on the integration's page, linked to a project. On GitHub, also check that the App was granted access to that repository.
Is the webhook reaching transglot? (GitLab, Bitbucket, Azure Repos)
Open the webhook's delivery history on the host. Each delivery must go to the URL shown on the transglot page, carry the same secret you saved on the connection, and be for a push event. A rejected delivery means the secret does not match: set the same value on both sides.
Does the account's plan include it?
Repository sync needs the Team plan or above. On a lower plan, pushes are not processed, and the GitLab, Bitbucket and Azure Repos cards say so, for example "The GitLab integration is not included on the current plan." See Plan requirements.
Is automatic translation on?
Strings are extracted whatever your settings, but they are only translated automatically if the project has automatic translation turned on. Otherwise they wait in the project until someone translates them, and there is nothing new for a pull request. See AI translation settings.
Is there AI translation allowance left?
If the workspace has used its AI translation allowance for the cycle and usage-based billing is off, extraction still runs but translation is skipped. GitHub records "Monthly word quota exceeded. Translation skipped." See usage-based billing.
Can the token still write? (GitLab, Bitbucket, Azure Repos)
A token that expired or lost permissions fails on the way back, not on the way in: strings can arrive in the project while no merge or pull request ever appears. Create a new token with write access and save it on the connection.
Is a pull request waiting for you?
The result is a merge or pull request from transglot's transglot/sync branch, never a commit to yours. Until someone merges it, nothing reaches your default branch. Look for an open request from transglot/sync.
Related
Connect GitLab, Bitbucket or Azure Repos
Connect a GitLab, Bitbucket or Azure Repos repository so a push to the default branch comes back as a merge or pull request with translations.
Connect a content platform
Pull content out of the CMS, store, help center or marketing tool it already lives in, translate it in transglot, and send reviewed translations back where the platform allows it.