To sync branches that are not the main branch of the repository, you need to select the branch you want to sync as the main branch on both the parent and forked repository. No other branch changes will be detected or available to sync. Only the main branch of the repository is synced with your fork. To sync your fork with the original repository, click the Sync button at the bottom of the Repository details pane. If your fork is behind on commits, the Sync button displaying the number of outstanding commits will be displayed at the bottom of the Repository details pane on the rightmost sidebar. These changes do not appear in your fork automatically you need to sync the fork in order to pull in any outstanding commits. Sync your forkĪfter you fork a repository, the original repository is likely to evolve as other users commit changes to it. The system creates the fork and opens the repository's Source page. You can avoid the impact to your plan by making your fork private or by not inheriting the users from the original repo.įorking: Choose whether you want to allow only private forks. Forking a public repo under your account can cause you to go over the limit on your Bitbucket plan. For example, if 4 accounts have access to the original your fork will give them the same access. Permissions: By default, your fork inherits the user/group permissions. An administrator of the original repository can prevent public forks In this case, then you cannot change the access. You can change this, making your fork private. So, if the original is public your fork is too. Name: This is the name the forked repo will have.Īccess level: By default, the system creates your fork with the same access level as the original. If you have the rights to create repositories in more than one workspace, this is a drop-down. Workspace: This defaults to the logged-in account. In the Fork dialog, define the options for your fork. Select Fork this repository from the dropdown menu. Go to a repository, select the More options ( ) button in the upper-right corner.

The final step in the workflow is for the owner of the original repository to merge your changes. Push changes back to the remote fork on Bitbucket.Ĭreate a pull request from the forked repository (source) back to the original (destination). Here is the basic workflow:Ĭlone the forked repository your local system. Forking is particularly useful if you want to do some major development work that you may or may not later merge back into the repository. Bitbucket Cloud manages the relationship between the original repository and the fork for you. To fork is just another way of saying clone. If you want to work on a completely separate copy of the project, you may want to consider creating a 'fork'.įorking is a way for you to clone a repository at a specific point, and to modify it from there. When you do this, your changes become part of the main project repository. In Git, you create branches by starting with either the head/trunk or an existing branch.

Github desktop fork