Because I learned that 10000 offline ephemeral self hosted runners is a funny thing

A command-line tool to delete GitHub self-hosted runners from a repository using the GitHub API.

• 🗑️ Batch deletion of all self-hosted runners in a repository or organization
• 🏢 Organization-level support - Delete all runners across an entire organization
• 🔍 Dry run mode to preview what would be deleted
• 📴 Offline-only mode - Filter to delete only offline runners
• 📄 Pagination support to handle repositories with many runners
• 🎨 Colorful output with clear status indicators
• ✅ Safety prompts to prevent accidental deletions
• 🔐 Token-based authentication with environment variable support

git clone <repository-url>
cd ghr-destroy
cargo build --release

The binary will be available at target/release/ghr-destroy.

ghr-destroy --owner myorg --token ghp_your_token_here

ghr-destroy --owner myorg --repo myrepo --token ghp_your_token_here

export GITHUB_TOKEN=ghp_your_token_here
ghr-destroy --owner myorg --repo myrepo

Preview what would be deleted without actually deleting:

ghr-destroy --owner myorg --repo myrepo --dry-run

Delete all runners without confirmation prompts:

### Delete Only Offline Runners

Target only offline runners for deletion:

```bash
# Organization level - offline runners only
ghr-destroy --owner myorg --offline-only
# Organization level
ghr-destroy --owner myorg --yes
# Repository level
ghr-destroy --owner myorg --repo myrepo --yes
### Custom Pagination

Fetch more runners per page (default is 100):

```bash
ghr-destroy --owner myorg --repo myrepo --per-page 50

*Required unless set via GITHUB_TOKEN environment variable

Your GitHub personal access token needs the following permissions:

• admin:org - To manage organization runners
• repo - To access repository information

• repo - Full repository access

1. Go to GitHub Settings → Developer settings → Personal access tokens
2. Click "Generate new token (classic)"
3. Select the required scopes listed above
4. Copy the generated token

This tool uses the following GitHub REST API endpoints:

• List runners: GET /repos/{owner}/{repo}/actions/runners
• Delete runner: DELETE /repos/{owner}/{repo}/actions/runners/{runner_id}

ghr-destroy -o myorg -r myrepo -t ghp_token123

ghr-destroy -o myorg -r myrepo -t ghp_token123 --dry-run

ghr-destroy -o myorg -r myrepo -t ghp_token123 -y

# Organization level - offline runners only (with confirmation)
ghr-destroy -o myorg -t ghp_token123 --offline-only

# Repository level - offline runners only (dry run)
ghr-destroy -o myorg -r myrepo -t ghp_token123 --offline-only --dry-run

# Organization level - offline runners only (skip confirmation)
ghr-destroy -o myorg -t ghp_token123 --offline-only --yes

The tool handles various error scenarios:

• Invalid token: Clear error message about authentication
• Repository not found: 404 errors are reported clearly
• Insufficient permissions: Permission errors are explained
• Network issues: Connection and timeout errors are handled
• Rate limiting: API rate limit errors are reported

The tool provides colorful, informative output:

• 🔄 Busy runners are indicated with a spinning icon
• 💤 Idle runners are shown with a sleep icon
• 🟢 Online status in green
• 🔴 Offline status in red
• 🟡 Unknown status in yellow

• Confirmation prompt before deletion (unless --yes is used)
• Dry run mode to preview operations
• Clear output showing exactly what will be deleted
• Error reporting for failed deletions

1. Fork the repository
2. Create a feature branch
3. Make your changes
4. Add tests if applicable
5. Submit a pull request

[Add your license information here]

⚠️ Warning: This tool will permanently delete GitHub self-hosted runners. Use with caution and always test with --dry-run first!