HTTP/2 200
access-control-allow-origin: *
content-security-policy: default-src 'none';prefetch-src 'self';connect-src 'self';font-src 'self' data:;img-src 'self' github.com *.github.com *.githubusercontent.com *.githubassets.com data: placehold.it;object-src 'self';script-src 'self' github.com *.github.com *.githubusercontent.com *.githubassets.com 'self' data:;script-src-attr 'self';frame-src 'self' github.com *.github.com *.githubusercontent.com *.githubassets.com https://support.github.com https://www.youtube-nocookie.com;frame-ancestors 'self' github.com *.github.com *.githubusercontent.com *.githubassets.com;style-src 'self' github.com *.github.com *.githubusercontent.com *.githubassets.com 'self' 'unsafe-inline' data:;child-src 'self';manifest-src 'self';upgrade-insecure-requests;base-uri 'self';form-action 'self'
cross-origin-opener-policy: same-origin
cross-origin-resource-policy: same-origin
origin-agent-cluster: ?1
referrer-policy: no-referrer-when-downgrade
x-content-type-options: nosniff
x-dns-prefetch-control: off
x-download-options: noopen
x-frame-options: SAMEORIGIN
x-permitted-cross-domain-policies: none
x-xss-protection: 0
cache-control: public, max-age=60
x-powered-by: Next.js
content-type: text/html; charset=utf-8
x-github-backend: Kubernetes
x-github-request-id: 8EF8:36C819:47F545:7374E7:687B3F9C
content-encoding: gzip
accept-ranges: bytes
age: 0
date: Sat, 19 Jul 2025 06:48:59 GMT
via: 1.1 varnish
x-served-by: cache-bom4720-BOM
x-cache: MISS
x-cache-hits: 0
x-timer: S1752907739.034826,VS0,VE385
vary: Accept-Encoding
strict-transport-security: max-age=31557600
content-length: 23257
Working with forks - GitHub Docs Skip to main content Commit changes to your project Collaborate with pull requests
Working with forks Forks are often used in open source development on GitHub.
A fork is a new repository that shares code and visibility settings with the original “upstream” repository.
A fork is a new repository that shares code and visibility settings with the original “upstream” repository.
The permissions and visibility of forks depend on whether the upstream repository is public or private, and whether it is owned by an organization.
You must configure a remote that points to the upstream repository in Git to sync changes you make in a fork with the original repository. This also allows you to sync changes made in the original repository with the fork.
Sync a fork of a repository to keep it up-to-date with the upstream repository.
For greater collaboration, you can allow commits on branches you've created from forks in your personal account.
Deleting your repository or changing its visibility affects that repository's forks.
You can disconnect a repository from its fork network by leaving the network or manually deleting the fork and recreating it without any connection to the original.
Help and support Ask Copilot your question. Ask Copilot
