-
Notifications
You must be signed in to change notification settings - Fork 67
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
Check release sometime fails to find remote ref #593
Comments
I was under impression that this happens when closing and reopening some PRs. |
That's what we often do on the JupyterLab repo after a Galata snapshot update, but not sure to have seen on https://github.com/jupyterlab/jupyterlab yet? |
It did pop up a couple of times, here for example: jupyterlab/jupyterlab#16866. The workaround I was using was to merge with |
It started appearing a month ago or so, I think this was a change in GitHub API behaviour. |
Good to know. I wonder if there is something we can do in the releaser to handle this new behavior. |
I hadn't noticed it.
Thanks, this is a better workaround than closing the PR, as long as it is not handled in the releaser. |
Description
Sometime the
prep-git
action fails with an error relative to the remote ref, for example in jupyterlab/jupyter-collaboration#378:fatal: couldn't find remote ref refs/pull/378/merge
.The workaround is to close the PR and open a new one.
Error log
Reproduce
This seems to be random, so difficult to reproduce.
Context
The text was updated successfully, but these errors were encountered: