Forking a repository is a simple process that allows you to propose changes to the original repository. In this guide, we will walk you through the process of forking the Hummingbot repository on GitHub.
A fork is a new repository that shares code and visibility settings with the original upstream repository. Forks are often used to iterate on ideas or changes before they are proposed back to the upstream repository, such as in open source projects or when a user does not have write access to the upstream repository.
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:
Under Owner," select the dropdown menu and click an owner for the forked repository.
By default, forks are named the same as their upstream repositories. Optionally, to further distinguish your fork, in the Repository name field, type a name.
Optionally, in the Description field, type a description of your fork.
Optionally, select Copy the DEFAULT branch only. For many forking scenarios, such as contributing to open-source projects, you only need to copy the default branch. If you do not select this option, all branches will be copied into the new fork.