Deletion workflows
- Single-delete mode for focused cleanup tasks.
- Multi-delete mode for batch operations on stale repositories.
- Typed confirmation gates for high-impact actions.
- Clear cancellation paths using standard terminal controls.
Features deep dive
RepoAnt helps teams delete repositories fast while preserving what matters.
This page explains how RepoAnt balances speed and caution when working with irreversible actions in GitHub.
Safety controls
- Protected repositories are excluded from delete lists.
- Warnings and prompts reduce accidental destructive actions.
- Predictable command behavior that is easy to audit.
- Designed for deliberate, explicit repository removal.
Security model
- Personal Access Token stored as a local file with 0600 permissions.
- No external token vault dependency required for solo workflows.
- Simple local configuration that is easy to inspect and reset.
- Token is never embedded in command history by default workflows.
Platform coverage
- Runs on macOS, Linux, and Windows.
- Homebrew installation path for macOS and Linux users.
- Source build path for custom setups and CI environments.
- Portable usage style that fits standard terminal habits.
FAQ
What token scopes does RepoAnt require?
Use a GitHub Personal Access Token with repo and delete_repo scopes.
Can I prevent critical repositories from being deleted?
Yes. Add repositories to the protected list and they will not appear in deletion selections.
Is RepoAnt suitable for batch cleanups?
Yes. Multi-delete mode is designed for bulk cleanup, with confirmation text that includes repository count before execution.