Troubleshooting
My repository sync is not running
Check the branch, the file pattern and the project link, and remember the result is a pull request somebody has to merge.
Work through these checks in order. For the full walkthrough, see Why is my repository sync not running?
- Was the push to the default branch? Strings are extracted from pushes to the repository's default branch only. A push to any other branch does nothing.
- Did the push change a file the link watches? Each repository link names a source file path and a format. A change to any other file is not picked up.
- Is the repository linked to a project? Installing the app or adding a connection is half of it: a repository with no project link has nowhere to put strings. The integrations screen lists linked repositories with their project.
- Is Auto-translate on? Strings are extracted either way, but they are only translated automatically while the project's Auto-translate setting is on. Otherwise they wait until someone starts a run.
- Is a pull request waiting? transglot never commits to your branches. On GitHub it commits the translated files to its own
transglot/syncbranch and opens, or updates, one pull request for the repository link once the translation run finishes. Nothing reaches your default branch until someone merges it. - Has the connection lost access? On GitLab, Bitbucket and Azure Repos the connection uses an access token. A token that expired or lost permissions can let extraction look fine while nothing ever comes back.
Related
My strings are not showing up in the editor
Check the filters first, then the language, then whether the push actually landed, in that order, because the first is by far the most common.
My translations are not reaching my app
Almost always because the language is translated but not published: editing and publishing are deliberately two different things.