Skip to content
BENIBIX Learn

Git Fork vs Git Clone

A fork is your copy of someone's repo on the website. A clone is a copy on your own computer, and you can clone a fork.

Development🔀 Version Control

Git Fork

Your own copy of someone else's repo, on the site. You are free to change it.

A fork is a copy of someone else's repo, made on a site like GitHub. It lives under your account, so you can push to it freely. This is how people help with projects they cannot write to directly. You make changes in your fork, then open a pull request to offer them back. The owner then decides whether to take them.

Example
Jack wants to fix a typo in a big open source project. He forks it, fixes the typo in his copy and sends a pull request.
Why it matters
Forks let anyone help with open source without needing to be let in first.
Full entry
Development🔀 Version Control

Git Clone

Your own full copy of a repo, with all of its past.

To clone is to copy a whole repo from a remote onto your computer. You get every file and the whole history, not just the latest version. Git also notes where the copy came from, as a remote named origin. Then you can work, commit and later push back. It is often the first thing you run when you join a team.

Example
Jack joins Emma's team. He clones the shop repo and has the full project, history included, in a few seconds.
Why it matters
Cloning is how anyone starts work on a shared project. Every clone is also a full backup.
Full entry

In one line

Git Fork
Your own copy of someone else's repo, on the site. You are free to change it.
Git Clone
Your own full copy of a repo, with all of its past.