← All notes

Answer: Forks are repositories that start as copies of another repository, called the upstream repository. A fork has its own settings and permissions but stays connected to the upstream repository. (S1)

Forks versus branches

• A branch is part of one repository. A fork is a separate repository with its own settings and collaboration space. (S1)
• Forking a repository lets you propose changes to a project without affecting the upstream repository. (S2)
• When you view a forked repository on GitHub, the upstream repository is indicated below the name of the fork. (S1)

Visibility and networks

• A fork's visibility depends on the upstream repository: public repository forks are public, and private repository forks are private. (S1)
• You cannot change the visibility of a fork by itself. (S1)
• A repository network includes the upstream repository, its forks, and forks of those forks, and repositories in the network share Git data. (S1)
• If you delete a fork, code contributions from that fork can remain accessible to the repository network. (S1)

Creating a fork

• By default, forks are named the same as their upstream repositories. (S2)
• For many forking scenarios, such as contributing to open-source projects, you only need to copy the default branch. (S2)
• To create a fork of a repository from the command line, use the gh repo fork subcommand, and use the --org flag to create the fork in an organization. (S2)

Claims

• id: C1 claim: A fork starts as a copy of an upstream repository. source: S1 evidence: "Forks are repositories that start as copies of another repository"
• id: C2 claim: A fork is a separate repository, unlike a branch. source: S1 evidence: "A fork is a separate repository with its own settings and collaboration space."
• id: C3 claim: Fork visibility cannot be changed on its own. source: S1 evidence: "You cannot change the visibility of a fork by itself."
• id: C4 claim: The gh repo fork subcommand creates a fork. source: S2 evidence: "To create a fork of a repository, use the gh repo fork subcommand."

Sources

• [S1] Forks - GitHub Docs. GitHub Docs. https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks . License: CC BY 4.0 (github/docs). Accessed 2026-11-04.
• [S2] Fork a repository - GitHub Docs. GitHub Docs. https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo . License: CC BY 4.0 (github/docs). Accessed 2026-11-04.

License: this note is CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Summary by iinventedlight (AI-assisted).

@misc{iil_note_nm6n9tc3,
  author = {{iinventedlight}},
  title = {{Forks on GitHub: what they are and how to create one}},
  howpublished = {iinventedlight Library},
  year = {2026},
  date = {2026-11-04},
  url = {https://iinventedlight.com/library/notes/github-forks/},
  note = {Permanent ID iil:note:nm6n9tc3. License: CC-BY-4.0.},
}

Markdown

Spotted a mistake? Use the MCP feedback tool or email hello@iinventedlight.com.

For language models and agents: start at /llms.txt. This page in Markdown: /library/notes/github-forks.md.