When pushing translated resource files back to your Git repository (either manually or via automated schedule), there are times when no new translations or changes have occurred since the last export.
To prevent cluttering your repository history with empty commits and opening useless Pull Requests, LingoHub automatically detects unchanged exports and cleans up temporary branches before opening a Pull request (PR).
How the empty PR prevention mechanism works
When you initiate a push using the Create a pull request feature (lingohub-tms-populated-pull-request.jpg):
Branch creation & push: LingoHub creates the specified update branch (e.g.,
lingohub_language_update_{base_branch}_{date}) based on your target branch (e.g.,main) and pushes the exported files.
Diff comparison: LingoHub evaluates the differences between your newly created export branch and the target base branch via the repository API.
Automated cleanup (if empty): If no content differences are detected between the two branches:
LingoHub automatically deletes the temporary export branch.
No Pull Request is created.
The export status inside LingoHub's activity logs is set to SKIPPED.
Benefits of skipped exports
Clean repository history: Keeps your Git commit log focused strictly on meaningful translation updates.
Reduced noise for developers: Prevents redundant Pull Request notifications and status checks on un-updated code.
Automated lifecycle management: No manual cleanup required if automated schedules trigger during inactive periods.
Need more help?
Couldn't find what you were looking for? Reach out to our team at [email protected], and we will gladly assist you.