About forks
Most commonly, forks are used to either propose changes to someone else's project to which you do not have write access, or to use someone else's project as a starting point for your own idea. You can fork a repository to create a copy of the repository and make changes without affecting the upstream repository. For more information, see "Working with forks."
Propose changes to someone else's project
For example, you can use forks to propose changes related to fixing a bug. Rather than logging an issue for a bug you have found, you can:
- Fork the repository.
- Make the fix.
- Submit a pull request to the project owner.
Use someone else's project as a starting point for your own idea.
Open source software is based on the idea that by sharing code, we can make better, more reliable software. For more information, see the "About the Open Source Initiative" on the Open Source Initiative.
For more information about applying open source principles to your organization's development work on your GitHub Enterprise Server instance, see GitHub's white paper "An introduction to innersource."
When creating your public repository from a fork of someone's project, make sure to include a license file that determines how you want your project to be shared with others. For more information, see "Choose an open source license" at choosealicense.com.
Para obter mais informações sobre código aberto, especificamente como criar e expandir um projeto de código aberto, criamos os Guias de Código Aberto, que ajudarão você a promover uma comunidade de código aberto benéfica, recomendando melhores práticas para criar e manter repositórios no seu projeto de código aberto. Você também pode fazer um curso gratuito de GitHub Skills sobre como manter comunidades de código aberto.
Prerequisites
If you have not yet, you should first set up Git. Don't forget to set up authentication to your GitHub Enterprise Server instance from Git as well.
Forking a repository
You might fork a project to propose changes to the upstream, or original, repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same octocat/Spoon-Knife repository you just forked.
- On your GitHub Enterprise Server instance, navigate to the octocat/Spoon-Knife repository.
- In the top-right corner of the page, click Fork.
- Select an owner for the forked repository.
- By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further.
- Optionally, add a description of your fork.
- Choose whether to copy only the default branch or all branches to the new fork. For many forking scenarios, such as contributing to open-source projects, you only need to copy the default branch. By default, only the default branch is copied.
- Click Create fork.
Note: If you want to copy additional branches from the parent repository, you can do so from the Branches page. For more information, see "Creating and deleting branches within your repository."
Para saber mais sobre a GitHub CLI, confira "Sobre a GitHub CLI".
To create a fork of a repository, use the gh repo fork subcommand.
gh repo fork REPOSITORYTo create the fork in an organization, use the --org flag.
gh repo fork REPOSITORY --org "octo-org"Cloning your forked repository
Right now, you have a fork of the Spoon-Knife repository, but you do not have the files in that repository locally on your computer.
-
On your GitHub Enterprise Server instance, navigate to your fork of the Spoon-Knife repository.
-
Acima da lista de arquivos, clique em Código.
-
Copie a URL do repositório.
- Para clonar o repositório usando HTTPS, em "HTTPS", clique em .
- Para clonar o repositório usando uma chave SSH, incluindo um certificado emitido pela autoridade de certificação SSH da sua organização, clique em SSH e em .
- Para clonar um repositório usando GitHub CLI, clique em GitHub CLI e selecione .
-
Abra TerminalTerminalGit Bash.
-
Altere o diretório de trabalho atual para o local em que deseja ter o diretório clonado.
-
Type
git clone, and then paste the URL you copied earlier. It will look like this, with your GitHub Enterprise Server username instead ofYOUR-USERNAME:$ git clone https://hostname/YOUR-USERNAME/Spoon-Knife -
Press Enter. Your local clone will be created.
$ git clone https://hostname/YOUR-USERNAME/Spoon-Knife > Cloning into `Spoon-Knife`... > remote: Counting objects: 10, done. > remote: Compressing objects: 100% (8/8), done. > remote: Total 10 (delta 1), reused 10 (delta 1) > Unpacking objects: 100% (10/10), done.
Para saber mais sobre a GitHub CLI, confira "Sobre a GitHub CLI".
To create a clone of your fork, use the --clone flag.
gh repo fork REPOSITORY --clone=true-
No menu Arquivo, clique em Clonar Repositório.
-
Clique na aba que corresponde � localização do repositório que você deseja clonar. Clique também na URL para inserir o local do repositório manualmente.
-
Escolha o repositório que você quer clonar na lista.
-
Clique em Escolher… e procure um caminho local em que deseja clonar o repositório.
-
Clique em Clonar.
Configuring Git to sync your fork with the original repository
When you fork a project in order to propose changes to the original repository, you can configure Git to pull changes from the original, or upstream, repository into the local clone of your fork.
-
On your GitHub Enterprise Server instance, navigate to the octocat/Spoon-Knife repository.
-
Acima da lista de arquivos, clique em Código.
-
Copie a URL do repositório.
- Para clonar o repositório usando HTTPS, em "HTTPS", clique em .
- Para clonar o repositório usando uma chave SSH, incluindo um certificado emitido pela autoridade de certificação SSH da sua organização, clique em SSH e em .
- Para clonar um repositório usando GitHub CLI, clique em GitHub CLI e selecione .
-
Abra TerminalTerminalGit Bash.
-
Change directories to the location of the fork you cloned.
- To go to your home directory, type just
cdwith no other text. - To list the files and folders in your current directory, type
ls. - To go into one of your listed directories, type
cd your_listed_directory. - To go up one directory, type
cd ...
- To go to your home directory, type just
-
Type
git remote -vand press Enter. You will see the current configured remote repository for your fork.$ git remote -v > origin https://hostname/YOUR_USERNAME/YOUR_FORK.git (fetch) > origin https://hostname/YOUR_USERNAME/YOUR_FORK.git (push) -
Type
git remote add upstream, and then paste the URL you copied in Step 3 and press Enter. It will look like this:$ git remote add upstream https://hostname/ORIGINAL_OWNER/Spoon-Knife.git -
To verify the new upstream repository you have specified for your fork, type
git remote -vagain. You should see the URL for your fork asorigin, and the URL for the original repository asupstream.$ git remote -v > origin https://hostname/YOUR_USERNAME/ YOUR_FORK.git (fetch) > origin https://hostname/YOUR_USERNAME/YOUR_FORK.git (push) > upstream https://hostname/ORIGINAL_OWNER/ ORIGINAL_REPOSITORY.git (fetch) > upstream https://hostname/ORIGINAL_OWNER/ ORIGINAL_REPOSITORY.git (push)
Now, you can keep your fork synced with the upstream repository with a few Git commands. For more information, see "Syncing a fork."
Para saber mais sobre a GitHub CLI, confira "Sobre a GitHub CLI".
To configure a remote repository for the forked repository, use the --remote flag.
gh repo fork REPOSITORY --remote=trueTo specify the remote repository's name, use the --remote-name flag.
gh repo fork REPOSITORY --remote-name "main-remote-repo"Editing a fork
You can make any changes to a fork, including:
- Creating branches: Branches allow you to build new features or test out ideas without putting your main project at risk.
- Opening pull requests: If you are hoping to contribute back to the original repository, you can send a request to the original author to pull your fork into their repository by submitting a pull request.
Find another repository to fork
Fork a repository to start contributing to a project. You can fork a private or internal repository to your personal account or an organization on your GitHub Enterprise Server instance where you have repository creation permissions, if settings for the repository and your enterprise policies allow forking.
Next Steps
You have now forked a repository, practiced cloning your fork, and configured an upstream repository.
-
For more information about cloning the fork and syncing the changes in a forked repository from your computer, see "Set up Git."
-
You can also create a new repository where you can put all your projects and share the code on GitHub. A criação de um repositório para seu projeto permite que você armazene código no GitHub. Isso fornece um backup do seu trabalho que você pode optar por compartilhar com outros desenvolvedores. Para obter mais informações, confira "Criar um repositório"."
-
Cada repositório em GitHub pertence a uma pessoa ou organização. Você pode interagir com as pessoas, repositórios e organizações, conectando-se e seguindo-as em GitHub Enterprise Server. Para obter mais informações, confira "Seja social".
-
O GitHub tem uma ótima comunidade de suporte na qual você pode pedir ajuda e conversar com pessoas de todo o mundo. Participe da conversa na GitHub Community.