A fork is an independent copy of a software project, made from its source code and evolved separately, without depending on the original project's choices.
On GitHub or GitLab, forking a repository is an everyday move: you create your own copy, make your changes there, then propose merging them back into the original project through a pull request (or merge request). It is the basic mechanism of open-source contribution.
The word also has a stronger meaning: a split. When part of the community disagrees with a project's direction (governance, license, acquisition), it forks it and carries it on under another name. Well-known examples:
- LibreOffice, from OpenOffice
- MariaDB, from MySQL
- OpenSearch, from Elasticsearch
Not to be confused with a clone, which is simply a local copy of a repository to work on.
Why it matters when hiring
Git vocabulary (fork, branch, pull request, merge) is a prerequisite for any developer, not a differentiator. The real signal lies elsewhere: accepted contributions to third-party open-source projects, visible on GitHub, show that a candidate can read code they did not write and follow another team's standards. A profile full of forks with no commits says nothing.
