-
-
Notifications
You must be signed in to change notification settings - Fork 357
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
Cleanup step fails to complete #365
Comments
Does the action properly make the deployment? If not I'm guessing this isn't the actual error and it's failing higher up in the process. My gut reaction is it's to do with your use of an ssh key and the |
There's also this. Looks like it's attempting to run a pre-commit hook that's throwing the error. |
I'm having a similar issue with
Overall I can't tell why this happens. It used to work, I tried with those versions but no luck. I'm getting this even with a clean installation after removing the cache. |
I see no reason to not add the no-verify flag as the default option, this will make the deployment more predictable. I'm happy to add this either later today or early tomorrow. |
Thanks! If you don't want it to change existing functionality, the ability to extend the command with custom parameters would also be an option. |
I can't think of a situation where a pre-commit hook would/should be used in conjunction with the commands it performs, but maybe I'm missing something? |
Me neither really. :) |
That would probably solve our problem too, thanks! |
Released as part of this update: https://github.com/JamesIves/github-pages-deploy-action/releases/tag/3.5.9 |
Thanks a lot for the quick fix! |
Thanks very much, indeed! |
I'm still facing this error (even after bumping to the latest version). This is weird because it is working fine on a few jobs and errors randomly. (link) Is there a way to fix this? Thank you. |
Could we catch the git error and print it out, to make debugging easier? |
It gets printed right before the generic git error; @SooluThomas Can you turn disable |
Yes, it worked. Thank you!! |
@JamesIves it's failing again :( |
Can you link me to the workflow failures so I can debug? |
In our workflow we are seeing the following error:
It seems like git should be able to remove the worktree, so I'm not sure why it is failing.
The text was updated successfully, but these errors were encountered: