Skip to content
Discussion options

You must be logged in to vote

Here are a two things you can try to resolve the issue:

  1. Try deleting the repository via the GitHub CLI

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-trigger

Make sure you’re authenticated with gh auth login first if you haven’t used the CLI before.

  1. Force a refresh on the GitHub backend

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.

Replies: 4 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by jabbson
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies

This comment was marked as spam.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Repositories The core of version-controlled code storage Question Ask and answer questions about GitHub features and usage
4 participants