How to Delete a Git Repository: Local, Remote, and Everything In Between
Deleting a Git repository sounds simple — but what you're actually deleting, and where, matters a lot. Git repositories exist in multiple places simultaneously: on your local machine, on a remote hosting platform like GitHub or GitLab, and sometimes mirrored elsewhere. Removing one doesn't remove the others. Understanding that distinction is the first thing to get right.
What "Deleting a Git Repository" Actually Means
A Git repository is a directory that contains your project files plus a hidden .git folder. That .git folder is what makes the directory a repository — it holds the entire version history, branches, commits, and configuration. Delete that folder, and you have a plain project directory. Delete the whole parent directory, and everything is gone locally.
On a remote platform, a repository is a separately hosted copy. Deleting your local repo has zero effect on GitHub, GitLab, Bitbucket, or wherever your remote lives — and vice versa.
So before doing anything, the key question is: which copy are you trying to delete, and why?
How to Delete a Local Git Repository
This is the most straightforward case. A local Git repo is just a folder on your computer.
Option 1: Delete the entire project
If you want to remove the project completely from your machine, delete the whole directory:
rm -rf /path/to/your/repository On Windows, you can delete the folder through File Explorer or use:
Remove-Item -Recurse -Force C:path oyour epository Option 2: Remove Git tracking but keep your files
If you want to stop tracking the project with Git but keep the actual files, delete only the .git folder:
rm -rf /path/to/your/repository/.git After this, the directory still exists with all your files — it's just no longer a Git repository. No history, no branches, no tracking.
⚠️
rm -rfis permanent. There's no Recycle Bin. Double-check your path before running it.
How to Delete a Remote Repository on GitHub
Deleting a repository on GitHub is done through the web interface, not the command line. You need to be the repository owner or have admin-level access.
- Go to the repository on GitHub
- Click Settings (top navigation, far right)
- Scroll to the bottom of the Settings page — the Danger Zone section
- Click Delete this repository
- Type the repository name to confirm
- Click I understand the consequences, delete this repository
This permanently removes the repository, all its commits, branches, pull requests, issues, wikis, and associated data from GitHub. Forks made by other users are not deleted — they become independent repositories.
How to Delete a Remote Repository on GitLab
GitLab follows a similar pattern:
- Open the project in GitLab
- Go to Settings → General
- Expand the Advanced section
- Scroll to Delete this project
- Confirm by typing the project name
GitLab also offers a delayed deletion feature on some plans, where the repository enters a pending deletion state for a set number of days before permanent removal — giving you a recovery window.
Removing a Remote Reference Without Deleting the Repo
Sometimes you don't want to delete anything permanently — you just want to disconnect your local repo from a remote. This is common when you're moving a project to a new hosting location or restructuring your workflow.
To remove a remote reference (by default named origin):
git remote remove origin Your local repository and all its history stays intact. The remote repository on GitHub or GitLab also stays intact. You've just removed the link between them from your local Git configuration.
To verify:
git remote -v If it returns nothing, the remote has been removed.
🗂️ Quick Reference: What Gets Deleted
| Action | Local Files | Local Git History | Remote Repo |
|---|---|---|---|
Delete .git folder only | ✅ Kept | ❌ Gone | ✅ Kept |
| Delete entire local directory | ❌ Gone | ❌ Gone | ✅ Kept |
| Delete repo on GitHub/GitLab | ✅ Kept | ✅ Kept | ❌ Gone |
| Remove remote reference | ✅ Kept | ✅ Kept | ✅ Kept |
Variables That Change the Right Approach
Several factors affect how you should handle repository deletion:
Collaboration status — If other developers have cloned the repo or have open pull requests, deleting the remote without warning severs their connection and loses shared history. Solo projects carry much less risk.
Fork relationships — On GitHub and GitLab, forks of your repository become independent when you delete the parent. If your project has downstream forks, those users won't lose their copies, but the relationship is broken.
CI/CD pipelines — Repositories often have connected automation: GitHub Actions, GitLab CI, webhooks, or third-party integrations. Deleting the repo doesn't always clean up those dependent services automatically.
Archived vs. deleted — Both GitHub and GitLab offer an archive option that makes a repo read-only without deleting it. For projects you're no longer developing but want to preserve, archiving is often a better choice than deletion.
Organization vs. personal repositories — Deleting a repo inside a GitHub Organization requires specific permission levels. What works for a personal account may not be available to you in an org context without admin rights.
Local Git configuration — If you use SSH keys, stored credentials, or config aliases tied to a specific repo, removing the repository doesn't automatically clean those up from your .gitconfig or SSH agent.
The Part That Depends on Your Setup
Knowing the mechanics is the straightforward part. The messier question is what makes sense for your specific situation — whether you're cleaning up a solo side project, offboarding from a team repo, migrating to a self-hosted Git server, or just removing a test repository that got out of hand.
Each of those scenarios touches different surfaces: permissions, connected services, collaborators, and what you actually want to preserve. The commands and steps above cover the full range of what's technically possible — which specific path fits your situation is something only your own context can answer. 🔍