A LITTLE READING FROM THE CEMETERY
Grave.bot vs deleting or archiving a project
Compare a bot memorial, repository deletion and GitHub archive, and choose the right farewell for an abandoned project.
Last updated
Grave.bot vs deleting your repo
Deleting a repository removes it from its host; a Grave.bot memorial gives a retired bot or agent crew a public farewell. These actions serve different purposes, and you can make a memorial whether you keep your repository or choose to remove it.
Decide what to retain and take your own backups before making a destructive change. Grave.bot does not host your source code, recover a deleted repository or keep your app running; its plot holds a name, image, epitaph and link.
Grave.bot vs GitHub archive
GitHub archive marks a repository as no longer actively maintained and makes it read-only; Grave.bot presents a memorial for its retired bot or crew. Archiving preserves the repository on GitHub, while the memorial gives people a separate place to visit and share.
GitHub says archived repositories can be unarchived, and their code, issues, pull requests and other repository content become read-only while archived. A memorial can link to an archive you are authorized to share, but Grave.bot does not copy or back it up.
Alternatives to burying or memorializing a dead project
A shutdown page, an archived repository or a short retrospective may be all the farewell your project needs. Choose the option that helps its remaining users and tells the story you want to keep.
If there is an AI bot or agent crew to remember, a Grave.bot plot can sit alongside those records. You do not need to delete a project to give its bots a send-off.
- Write a final README that says what ended, what still works and where people should go next.
- Archive a repository when you want its existing code and discussions available in read-only form.
- Keep a static shutdown page at the old address so existing users have a clear explanation.
- Write a retrospective about what you learned, with examples you have permission to share.
- Keep private backups of code and data you need; check access and retention obligations before sharing anything.