Repository navigation
Do not commit and force push when no changes are made #296
Description
Is your feature request related to a problem? Please describe.
We are looking at migrating from the native github-integration in Crowdin to using this action to maintain least privilege permissions in a better way and attribute the commits to an app/bot user.
With the native integration we could have the sync set to every hour, and nothing would happen in the repo unless there were actual changes. These changes would also be committed as new commits in the localization branch and appended to the pull request.
When running this action, a new commit is created and force pushed on every run, even though no more changes have been made since last time the action was run.
Describe the solution you'd like
For each workflow run, the action should commit and push any additional changes to the localization branch. If, after downloading translations, the localization branch does not have any changes - a commit is not necessary and should not be done.
Describe alternatives you've considered
The alternative would be to build a custom action with the required logic, but we would like to avoid that.
Additional context
Add any other context or screenshots about the feature request here.
Activity
omgovich commentedon Nov 7, 2025
We are having the same problem. Scheduled calls of the action force push the same translations and trigger the rest of the CI checks as well as unnecessary GitHub notifications.
fix: skip commit and push when no changes compared to remote
andrii-bodnar commentedon Jan 12, 2026
Hi @eriktm, @omgovich!
I've pushed a fix for this in the
fix/skip-push-when-no-changesbranch (#300)What changed:
The action now fetches the remote localization branch before checkout, ensuring that downloaded translations are compared against the actual remote branch state (not the base branch). This allows the existing "nothing to commit" check to work correctly and skip unnecessary commits/pushes.
To test before the next release:
Feedback is welcome! If testing goes well, this will be included in the next release.