Repo wouldn't disappear after deleting #164223
-
Select Topic AreaQuestion BodyI tried to clone a repo template, and something went wrong with the process, because I ended up with a broken copy which looks like this: Now if I try to delete this, I don't get any errors, and the message confirms the repo was deleted: when I come back to the list, it is still there: I tried to reload, clear cache and re-login without any result. Happy to hear your thoughts on what else I could try. I think something is terribly broken about this repo on the backend, because it also wouldn't change the visibility (I thought I would just make it private instead of deleting it). |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
|
Here are a two things you can try to resolve the issue:
Sometimes the web UI doesn’t fully complete the operation if something went wrong in the background. Try this via terminal:
Make sure you’re authenticated with gh auth login first if you haven’t used the CLI before.
Make a small change (like adding a README or editing the description) and save it. Sometimes this forces GitHub to "unstick" a broken repo state and deletion may then work. |
Beta Was this translation helpful? Give feedback.
-
|
If this also not work then try to add some readme or any file from CLI or other means and if those files are added then try again to delete the Repo but this time from CLI ,not from GUI |
Beta Was this translation helpful? Give feedback.
-
|
@JonathanZawadke @Lg007-git thank you both for you answer. Marking @JonathanZawadke's response as answer, as deleting with GH cli helped. Appreciate your help. |
Beta Was this translation helpful? Give feedback.



Here are a two things you can try to resolve the issue:
Sometimes the web UI doesn’t fully complete the operation if something went wrong in the background. Try this via terminal:
gh repo delete jabbson/n8n-nodes-pushover-triggerMake sure you’re authenticated with gh auth login first if you haven’t used the CLI before.
Make a small change (like adding a README or editing the description) and save it. Sometimes this forces GitHub to "unstick" a broken repo state and deletion may then work.