Usually because the push was not to the default branch, the repository is not linked to a project, or the credential lost the permission it needs.
Who this is for
Anyone who pushed and expected translations back.
What happens next
Work through these.
Was the push to the default branch? Extraction runs on pushes to the default branch only. A push to a feature branch does nothing.
Did the push change a file the link watches? The link names a path pattern and a format. A change outside that pattern is not localization content as far as transglot is concerned.
Is the repository actually linked to a project? Installing the app or adding a connection is only half of it: a repository with no project link has nowhere to put strings. The integrations screen lists linked repositories with their project and last run.
Has the credential lost access? For the connected-token hosts, a token that expired or had its scope reduced will fail on the way back rather than on the way in, so extraction can appear to work while nothing ever comes back.
Is anything waiting for you? The result is a pull or merge request on transglot's own branch, not a commit to yours. If nobody merges it, nothing reaches your default branch.
Is auto-translate on? Strings are extracted regardless, but they are only translated automatically if the project has auto-translate enabled. Otherwise they sit untranslated until someone runs a translation.
Related
Connect GitHub
Connect GitLab, Bitbucket or Azure Repos
AI translation settings
