

Right click the master branch and select "Merge from.".You may have to commit all the current changes before you can switch branches. If not double click on master to make it the active branch.

Make sure that master is the active branch (it should be bold).Merging the changes from upstram/master branch into the local master branch Notice that this does not change any existing branch. This will fetch all the changes from the "upstream" repository and put them in the LOCAL repository. To pull the latest changes and bring your fork up date: If you go to your fork's GitHub web page you will see that there is a line just before the description of the files in the repo that indicates if your fork is ahead, behind or in sync with the master branch of the original repo. Sooner or later, the main repo will have updates that you will want to pull into your fork. Pulling updates from the main (upstream) repository This create a connection to the main repository named "upstream" that will allow us to get the latest change from it. Enter "upstream" in the name and the main repository url (i.e.Under "Remotes" sub-menu, click "Add" hyper-link.Click on "Repository Settings" hyper-link.Keeping your fork up to date with the main repository Create "upstream" remoteįirst, you need to add a second remote that refer to the original master repository. Notice that this is your own copy of the repository connected to the fork and not the main repository. This creates a local clone of your repository with the cloud repository is configured as the default remote named "origin"

This creates a copy of the repository under your GitHub account which you have read and write access.Ĭlone your forked repository to your local machine using Visual Studio.
