Skip to content

Update about-forks.md for clarity and style #40596

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
+13 −14
Closed

Update about-forks.md for clarity and style #40596

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d350b97
Update about-forks.md for clarity and style
SachinSingh008 Sep 28, 2025
f65b690
Merge branch 'main' into patch-2
SachinSingh008 Sep 29, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 13 additions & 14 deletions ...ull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: About forks
intro: A fork is a new repository that shares code and visibility settings with the original “upstream” repository.
intro: A fork is your personal copy of a repository that lets you experiment safely and propose changes to the original project.
redirect_from:
- /github/collaborating-with-issues-and-pull-requests/working-with-forks/about-forks
- /articles/about-forks
Expand All @@ -16,36 +16,35 @@ topics:

## About forks

Forks are like independent copies of repositories. Unlike branches, forks give you more freedom to experiment without affecting the original project. Unlike cloned or duplicated repositories, changes from forks can be merged back into the upstream repository via pull requests, similar to a branch.
A fork is an independent copy of a repository. It lets you experiment without affecting the original and propose changes via pull requests.

When you view a forked repository on {% data variables.product.github %}, the upstream repository is indicated below the name of the fork.
The upstream repository appears below the fork’s name on {% data variables.product.github %}.

![Screenshot of a repository's page on GitHub. Below the name of the repository, "mona/docs", the text "forked from github/docs" is outlined in orange.](/assets/images/help/pull_requests/fork-path.png)

## What makes forks distinct from branches
## How forks differ from branches

Each fork is a complete repository with its own:
Each fork has:

* Branches
* Members and discussions
* Its own branches
* Discussions and members
* Issues and pull requests
* Actions and projects
* Tags, labels, and wikis

## When to use a fork

There are times when a fork may be a better fit for your task than a branch would be. A fork might be better:
Use a fork to:

* To experiment safely without affecting the original project
* To create separate space for discussions unrelated to a project's main goals
* When you might want to make your work an independent repository later
* Experiment safely
* Hold separate discussions
* Make your work independent

## Which repositories can be forked?

{% data reusables.repositories.you-can-fork %}

## Next steps

For instructions for forking a repository, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo).

For more information about when you can create forks, and the permission and visibility settings of forks, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-permissions-and-visibility-of-forks).
- [Fork a repository](/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo)
- [About permissions and visibility of forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-permissions-and-visibility-of-forks)
Loading