-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remote rejected: cannot lock ref #61
Comments
WorkaroundAs for the workaround, I've re-pulled and pushed again after the job failure.
But would be great to add some pull feature and re-try system to this action to try again, in case the remote HEAD changed. |
Hey @kenorb this really helped, thank you! |
i have the same issue, is there any planned fix for this ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following error can happen at random especially for jobs in parallel (matrix). This could be related to race condition.
My config:
I don't want to force push (because obviously something changed upstream right after the pull), so maybe integrating pull feature as well right before push could be useful and do some customizable number of retries?
One workaround is to move push action outside of matrix jobs by uploading changed from from matrix job, then downloading artifacts (e.g. patches) and push the changes at the final stage.
The text was updated successfully, but these errors were encountered: