You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
v2.11.0 introduces the side-effect to cause the succeeding github steps to run on the improper commit. #310
Describe the bug
Since this https://github.com/crowdin/github-action/releases/tag/v2.14.1 version, the crowdin action checkouts the latest commit where the crowdin translastion files were changed, instead of the latest commit in the base branch.
To Reproduce
Steps to reproduce the behavior:
Configure the GitHub workflow as the README suggests:
Specify the crowdin/github-action@v2 as the target version.
Expected behavior
The crowdin/github-action@v2 should checkout back to the state where the actions/checkout@v4 is, to prevent the succeeding Github steps running on the improper commit.
I just created PR #311. Could you please take a look?
It would also be great if you could try it referencing my branch (- uses: crowdin/github-action@fix/restore-checkout-after-l10n-push) and see if it works for you.
Activity
andrii-bodnar commentedon Apr 21, 2026
HI @sakurawald, thanks for reporting this!
I just created PR #311. Could you please take a look?
It would also be great if you could try it referencing my branch (
- uses: crowdin/github-action@fix/restore-checkout-after-l10n-push) and see if it works for you.sakurawald commentedon Apr 21, 2026
Thank you for your quick fix.
It now works the same as the version before v2.11.0.
andrii-bodnar commentedon Apr 22, 2026
@sakurawald thank you for the confirmation!
andrii-bodnar commentedon Apr 22, 2026
Available in
v2.16.1andv2