Delete a GitHub Gist Safely with gh gist delete

One wrong ID and the gist you needed is gone, with no undo. gh gist delete removes a GitHub gist from the command line, and this guide keeps the destructive choice in plain view so you check before you commit. Allow about five minutes for a known gist ID, or ten if you need to identify it first.

The examples use gh 2.87.3, installed here on 23 September 2026.

• You need an authenticated gh session. It must have permission to delete the gist.
• Run it as your ordinary user. Do not use sudo: changing the user can make gh read a different configuration and credential store.

1. Check the installed command

Confirm which executable will run and read its local help:

$ command -v gh
/usr/bin/gh
$ gh --version
gh version 2.87.3 (2026-02-23)
$ gh gist delete --help

The installed synopsis is gh gist delete {<id> | <url>} [flags]. It accepts one gist ID or URL, or no argument for an interactive selection. The only command-specific option in this version is --yes, which confirms deletion without prompting.

2. Identify the gist before deleting it

Use a full gist URL or its ID. A URL is often safer when you copy from a browser, because the owner and selected page stay visible during review:

$ gh gist view https://gist.github.com/EXAMPLE_OWNER/0123456789abcdef0123456789abcdef

Replace EXAMPLE_OWNER and the hexadecimal value with the real values. The view command is only a check; it deletes nothing. If you already have a verified ID, use it directly. Do not guess an ID, and do not paste a repository URL that is not a gist URL.

For an interactive choice, leave the selector empty and let gh retrieve your gists:

$ gh gist delete

The command presents a selection, then asks for confirmation using the gist's filename. Choose the exact gist, read the question, and answer yes only when its identity is clear. With no gists available, the current implementation reports No gists found. and deletes nothing.

3. Delete interactively at a terminal

The safest normal form is an explicit, verified selector without --yes:

$ gh gist delete https://gist.github.com/EXAMPLE_OWNER/0123456789abcdef0123456789abcdef
? Delete "notes.txt" gist? Yes
✓ Gist "notes.txt" deleted

The success marker can vary with your terminal colour scheme. The useful text is that the named gist was deleted. Answering no cancels the operation and returns a cancellation error. Treat that as a successful safety outcome, not as proof that a deletion happened.

4. Use --yes only in a reviewed script

Non-interactive jobs cannot answer a prompt. Pass both a verified ID or URL and --yes:

gist_url='https://gist.github.com/EXAMPLE_OWNER/0123456789abcdef0123456789abcdef'
gh gist delete "$gist_url" --yes

• No unreviewed inputs. Do not fill the placeholder from an unreviewed command substitution or an ambiguous search result.
• --yes is not a safety check. It suppresses the final confirmation and adds nothing in its place.
• Keep the selector reviewed. Use a reviewed configuration or an argument supplied by an operator.
• Without --yes, non-interactive runs fail. The command cannot prompt, so it fails before deleting.
• Without a selector, they fail too. The command needs an ID or URL when it cannot present an interactive choice.

5. Check the result and diagnose failures

When standard output is a terminal, a successful deletion prints the gist filename. For a script, the exit status is the better signal:

if gh gist delete "$gist_url" --yes; then
    printf '%s\n' 'Gist deletion completed'
else
    status=$?
    printf 'Gist deletion failed with status %s\n' "$status" >&2
    exit "$status"
fi

If the command says the gist was not found or is not owned by you, check the URL, the active GitHub account and the hostname in your gh configuration. A valid-looking ID is not evidence that the current account owns the gist. Fix authentication or network errors before retrying.

After a successful deletion, the same gist URL should no longer show the gist to you. That is a remote check and may produce an HTTP or GitHub error page rather than a useful shell message.

6. Keep a copy when recovery matters

There is no recovery command in this workflow, so save the content before deletion if you may need it. For a text gist, write its raw content to a deliberately named local file, then inspect that file before proceeding:

$ gh gist view https://gist.github.com/EXAMPLE_OWNER/0123456789abcdef0123456789abcdef --raw > gist-backup.txt
$ test -s gist-backup.txt && echo 'Backup is non-empty'
Backup is non-empty

The raw form may contain more than one file depending on the gist, so check the backup rather than assuming one filename.