A GitHub fork is a clone of a repository (repo) that is stored in your account instead of the account from which the data was forked. You own your forked copy after you fork a repo. This implies you can make changes to your split repository without affecting the parent source.
Select Clone Repository from the File menu.
Select the tab that corresponds to the repository you wish to clone from the drop-down menu.
From the list, select the repository you wish to clone.
Navigate to a local directory where you want to clone the repository by clicking Choose...
A fork is a manageable clone of a repository. Changes to a project can be made via forks without impacting the original repository. With pull requests, you can get updates from the original repository or make modifications to it.
If you're the owner of the organisation or have admin capabilities for the repository or fork, you can delete it. The upstream repository is not deleted when a forked repository is deleted.
A fork produces an entirely separate copy of a Git repository. A Git clone, unlike a fork, makes a linked copy that maintains synchronisation with the target repository.