If you have successfully set up a repository connection and pulling works fine, but pushing from LingoHub results in an error, the cause is usually related to permissions or branch restrictions.
Common causes for push failures
If your export/push to repository results in a failure state, please check the following common issues:
1. Insufficient permissions
The most common reason for a push failure is that the account connected to LingoHub lacks the necessary permissions for your repository.
To fix this, first verify your repository settings to see if your target branch is protected (which often blocks automated pushes).
If your main branch is restricted, a simple workaround is to push your translations to a dedicated feature branch, then manually create a Pull Request to merge the changes.
2. Protected branches
Many repository providers (such as GitHub, GitLab, and Bitbucket) use branch protection rules to ensure code quality. A push from LingoHub may fail if:
The branch is locked for everyone except specific users.
Pull requests/Merge requests are mandatory before code can be added to the branch.
Required status checks or reviews have not been completed.
Tip: Verify credentials. Ensure the integration user has “Write” access to both the repository and the repository provider’s API.
Awesome! You have finished the article about troubleshooting failed repository pushes. We hope this guide helped you identify the cause of the error. Otherwise, contact our support, and we will gladly help!