Delete forked repo from GitHub

GitGithub

Git Problem Overview


I'm starting with git and GitHub and there's a project I'm watching on GitHub. I unintentionally clicked to fork it. Now it appears as a new project to me.

I have some doubts about it:

  • I know if commit or do another thing to my forked repo, it will be updated, but the updated code will take effect only after the project's author request the pull. Right?
  • If I go to admin panel on GitHub there's a delete option. If I delete it as the option above, will it make any effect in the original one or not?

I'd like to delete it. By now I'm just studying the code and don't really need the fork.

Git Solutions


Solution 1 - Git

By far the easiest way is to log in GitHub account:

  1. Click to your repository for example yourUsername/yourRepository for example mbaric/zpropertyz.
  2. Then in the main toolbar of GitHub click on Settings
  3. Scroll to the bottom of the page to the section called Danger Zone and you will find Delete this repository button
  4. When you click it another pop up will appear here you need to type in your Github username and the name of your repository in this format gitHubUsername/nameOfTheRepository and click on the button below which says: I understand the consequences, delete the repository
  5. If you are having trouble doing it, below are the images that can be checked…

2020-01-15 - Here are images. Enjoy. GHD1

GHD2

GHD3

GHD4

Solution 2 - Git

Deleting it will do nothing to the original project. Editing it will only edit your fork on your repo page.

Solution 3 - Git

Just delete the forked repo from your GitHub account.

https://help.github.com/articles/deleting-a-repository/

  • If I go to admin panel on GitHub there's a delete option. If I delete it as the option above, will it make any effect in the original one or not?

> It wont make any changes in the original one; cos, its your repo now.

Solution 4 - Git

There will not be any harm deleting the forked repositories. You can again fork that. It won't change the original code. The flow is like this...

  1. You fork a repository. Just think of this as another copy of code which you can access or make changes to. The url of this repository will be of the form https://github.com/your-user-name/original-repo.

  2. You make some changes to that in your local machine and push them. Now the copy you created will be updated, but not the original one from which you have forked your repo.

  3. If you want the changes you added to your forked repo to be applied to original repo(this may be helpful to the people who are organizing the repo) then you have to create a pull request which you can do through UI. Then if they like your contribution, they will merge that with their code.

Generally this is what open source organizations do.

Solution 5 - Git

Sweet and simple:

  1. Open the repository
  2. Navigate to settings
  3. Scroll to the bottom of the page
  4. Click on delete
  5. Confirm names of the Repository to delete
  6. Click on delete

Solution 6 - Git

Deleting your forked repository will not affect the master (original) repository.

Like I have shown an example by deleting a forked repo.

This is my forked repo (Image)

Deleting the forked repo

And no changes to the original repository.

The master repo is something like an original one.

Forking is same as creating a xerox copy of the original one. Even if you get your xeroxed paper damaged, will it be that the original document also gets damaged? Obviously No.

So it's the same as that.

Solution 7 - Git

Answer is NO. It won't affect the original/main repository where you forked from. (Functionally, it will be incorrect if such an access is provided to a non-owner).

Just wanted to add this though.

> Warning: It will delete the local commits and branches you created on > your forked repo. So, before deleting make sure there is a backup of > that code with you if it is important.

Best way would be getting a git backup of forked repo using:

git bundle 

or other methods that are familiar.

Solution 8 - Git

select project to delete->settings->buttom click delete button->enter name of the repositories

Solution 9 - Git

Select repo->Settings->(scroll down)Delete repo

Solution 10 - Git

No, it will not affect your original repository, just make sure that the repo address looks like "youGitName/TheRepository" and not like "OtherPersonGitName/TheRepo".

Solution 11 - Git

Open the repository you want to delete on github and press the settings tab. Scroll to the end of the page and click on delete repository. Write the name of the Repository to confirm and click on delete like this one:

enter image description here

Solution 12 - Git

I was also looking for a solution to this problem, especially for bulk deletes. I finally used this solution - https://github.com/yangshun/delete-github-forks.

Worked like a charm!!

Solution 13 - Git

I had also faced this issue. NO it will not affect your original repo by anyway. just simply delete it by entering the name of forked repo

Solution 14 - Git

There are multiple answers pointing out, that editing/deleting the fork doesn't affect the original repository. Those answers are correct. I will try to add something to that answer and explain why in my answer.

A fork is just a copy of a repository with a fork relationship.

As you can copy a file or a directory locally to another place and delete the copy, it won't affect the original.

Fork relationship means, that you can easily tell github that it should send a pull request (with your changes) from your fork to the original repository because github knows that your repository is a copy of the original repository(with a few changes on both sides).

Just for anybodies information, a pull request(or merge request) contains code that has been changed in the fork and is submitted to the original repository. Users with push/write access(may be different in other git servers) on the original repository are allowed to merge the changes of the pull request into the original repository(copy the changes of the PR to the original repository).

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionaxcdntView Question on Stackoverflow
Solution 1 - GitMatijaView Answer on Stackoverflow
Solution 2 - GitConnerView Answer on Stackoverflow
Solution 3 - GitPrashanth SamsView Answer on Stackoverflow
Solution 4 - GitaravindkannaView Answer on Stackoverflow
Solution 5 - GitGurjot SinghView Answer on Stackoverflow
Solution 6 - GitPrateek ChandaView Answer on Stackoverflow
Solution 7 - GitSagar KulkarniView Answer on Stackoverflow
Solution 8 - GitNilavarasi AshikaView Answer on Stackoverflow
Solution 9 - GitAshik AzeezView Answer on Stackoverflow
Solution 10 - GitBruno MaiaView Answer on Stackoverflow
Solution 11 - GitShoaib KhalilView Answer on Stackoverflow
Solution 12 - Gitindranil32View Answer on Stackoverflow
Solution 13 - GitSHANKAR YADAVView Answer on Stackoverflow
Solution 14 - Gitdan1stView Answer on Stackoverflow