graveyardlisted

# Graveyard: archive and retire GitHub repos Help the user move repositories they no longer actively use into one private "graveyard" repo, preserving complete history as git bundles, then delete the originals — but only after each backup is verified. The result is a single, cheap-to-keep repo that is a full, restorable backup of many retired projects. ## Why git bundles A `git bundle` is a single file containing real git objects — commits, trees, blobs, refs. Unlike a zip of the working tree, a bundle preserves the entire history and can be cloned or fetched from directly (`git clone repo.bundle`). Mirror-cloning first (`git clone --mirror`) means the bundle captures **every** ref: all branches, all tags, and even GitHub's `refs/pull/*` merge refs. This is what makes deletion safe — the bundle is a faithful, restorable copy. ## The workflow Work through these phases interactively. This is the user's GitHub account and deletion is irreversible, so keep them in the loop at the decision points (which repos, and the final delete), and do the mechanical work yourself. ### 1. Confirm intent and scope Ask (or confirm from context): which account/owner, and roughly what they want gone. Confirm the graveyard repo name (default: `graveyard`) and that it should be **private** — this is a backup of code the user is removing from public/ normal view, so private is the safe default. ### 2. List candidate repos Show the user their repos so they can choose. Pull the fields that hel