-
-
Notifications
You must be signed in to change notification settings - Fork 483
ignore hook removal when repo is already deleted on github #5822
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
base: main
Are you sure you want to change the base?
Conversation
|
Thanks! For consistency reasons, it would be nice to have this for all forges and not just github. Can you try to check it out as fas as possible? If not, we can also take a look of course. But I'd rather not merge this with only fixing the issue for github. |
Yeah, that would be nice. But I wonder how to do this? Every forge might have another response if the repo is already deleted. Also the error interface only has a String, thus you cannot detect specific error for all repos. Any thoughts? |
This comment was marked as outdated.
This comment was marked as outdated.
|
No, I'd go with the approach you used already, for github: error handling inside the forge. But this needs to be added to the other forges as well. As you said a general solution won't work. |
I have added the same logic to gitea. But I fear I am done here. I don't have the possibility to test other forges as well and I don't like to commit code which I haven't tested before :( |
|
Would be better to use short variable names, like |
1 similar comment
|
Would be better to use short variable names, like |
Thanks, also |
Hi,
this fixes an "internal error" when trying to delete a repository in woodpecker which is already deleted on github.
Other forges might also be affected but I think it has to be fixed in every forge implementation itself because every forge will response differently.
see issue #5140
regards
Daniel