whatisgithub

What is delete-github-forks?

yangshun/delete-github-forks — explained in plain English

Analysis updated 2026-05-18

236JavaScriptAudience · developerComplexity · 2/5Setup · easy

In one sentence

A small command-line tool that lists your GitHub forks and bulk-deletes the ones you no longer want, avoiding the tedious one-by-one web deletion flow.

Mindmap

mindmap
  root((Delete GitHub Forks))
    What it does
      Lists your forks
      Bulk deletes forks
      Avoids manual cleanup
    Workflow
      Fetch fork list
      Review and edit file
      Run delete command
    Tech stack
      Node.js
      GitHub API
    Setup
      Access token needed
      Two required scopes
    Audience
      GitHub contributors

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Clean up a GitHub account cluttered with old contribution forks

USE CASE 2

Review a saved list of forks before deciding which to delete

USE CASE 3

Bulk-delete unwanted forked repositories through the GitHub API

What is it built with?

JavaScriptNode.jsGitHub API

How does it compare?

yangshun/delete-github-forksjuliangarnier/juliangarnier.comdimartarmizi/omnicloud
Stars236236230
LanguageJavaScriptJavaScriptJavaScript
Last pushed2025-01-21
MaintenanceStale
Setup difficultyeasyeasy
Complexity2/52/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

Requires a GitHub personal access token with repo read and delete permissions, deletions cannot be undone.

So what is it?

Delete GitHub Forks is a small utility for cleaning up forked repositories on your GitHub account. When you contribute to open-source projects, GitHub creates a copy of the original repository in your account called a fork. Over time, these forks accumulate and become clutter, but deleting them one by one through the GitHub website is tedious because you have to type your password and the repository name for each deletion. This tool solves that problem in two steps. First, you run a command that fetches a list of all your forked repositories and saves it to a local file. You then open that file, review the list, and manually remove any forks you want to keep. Whatever remains in the file will be deleted in the second step. The second step runs a delete command that reads the file and removes all the listed repositories from your GitHub account through the GitHub API. The README explicitly warns that this operation cannot be undone, so reviewing the file carefully before running the second command is important. Setup requires adding your GitHub username and an access token to a configuration file. The token needs two specific permissions: one to access your repositories and one to delete them. The project is simple by design. It does one thing and takes only a few minutes to run. The README notes that the scripts could be adapted to work on organization repositories as well, though that is not built in by default.

Copy-paste prompts

Prompt 1
Help me set up a GitHub access token with the right permissions for delete-github-forks
Prompt 2
Show me how to run delete-github-forks safely so I don't delete a fork I still need
Prompt 3
Explain how to adapt delete-github-forks to clean up organization repositories instead
Prompt 4
Walk me through the two-step list-then-delete workflow of this tool

Frequently asked questions

What is delete-github-forks?

A small command-line tool that lists your GitHub forks and bulk-deletes the ones you no longer want, avoiding the tedious one-by-one web deletion flow.

What language is delete-github-forks written in?

Mainly JavaScript. The stack also includes JavaScript, Node.js, GitHub API.

How hard is delete-github-forks to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is delete-github-forks for?

Mainly developer.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.