![commit to forked repo github desktop commit to forked repo github desktop](http://i.stack.imgur.com/mbJZZ.jpg)
Refresh your Github page and your fork should now be even (in sync) with the original repo.If for some reason this doesn’t work, try git push origin develop (or master). This pushes the changes from your local clone to your forked repo in GitHub. This merges all the changes from the original repo to your local clone. Again, substitute develop for whatever your main branch is.
![commit to forked repo github desktop commit to forked repo github desktop](https://www.testingdocs.com/wp-content/uploads/git-add.png)
This switches you to that branch in case you’re not there already. Otherwise you can set the upstream branch, but after that you’d need to explicitly pull from upstream: git branch -set-upstream origin/master. It may be called master, so type the appropriate command. If you want git pull without arguments to keep pulling from upstream you’ll need to explicitly push to your origin: git push origin master. This assumes the main branch of your repository is called develop. This fetches all the changes from the original repo. In the command line, move to your repository folder: cd repositoryname.So to update your forked repository, you will first pull in all the changes (commits) from the original repo into your local clone, and then push those changes to your fork. Process overview: Original repo –> Local clone –> ForkĪll changes are always made on the local clone and then pushed to the fork. Once you’ve set up the configuration, follow the steps below. Prerequisites: You need to configure git to sync your fork using the git remote add command. Your download of that fork onto your local drive is called a clone. Your forked copy of that repo is called origin. Recap: The original repository is referred to as upstream.