jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-19 18:10:59 -05:00
Code Issues Projects Releases Wiki Activity

Update about-forks.md: move a non-difference out of the list of diffe… (#38913)

Browse Source 
Co-authored-by: Sharra-writes <sharra-writes@github.com>
This commit is contained in:
GfEW
2025-06-17 17:59:34 +02:00
committed by GitHub
parent d29ffa4da8
commit 2c2fb031fa
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
View File

@@ -46,9 +46,10 @@ Forking a repository is similar to duplicating a repository, with the following
* Code pushed to a fork is visible to all repositories in the fork network, even after that fork is deleted.
* You can use a pull request to suggest changes from your fork to the upstream repository.
* You can bring changes from the upstream repository to your fork by synchronizing your fork with the upstream repository.
* Forks have their own members, branches, tags, labels, policies, issues, pull requests, discussions, actions, projects, and wikis.
* Forks inherit the restrictions of their upstream repositories. For example, branch protection rules cannot be passed down if the upstream repository belongs to an organization on a {% data variables.product.prodname_free_team %} plan.
Like duplicated repositories, forks have their own members, branches, tags, labels, policies, issues, pull requests, discussions, actions, projects, and wikis.
## Further reading
* [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models)