#Github desktop fork update how to

The instructions below show how to use the Git command-line tools to add the new remote and pick up changes. This is usually harmless, but it's better to avoid these unnecessary entries. This makes it very quick and easy to pick up new changes as frequently as you feel is necessary for your project.Įach time you use a GitHub pull request to update your fork, you create a new commit in your branch and a new pull request in your project's history. Once you've set up your upstream remote, you never have to set it up again as long as you keep using the same local clone of your fork. Then you can push those changes back up to your own fork on GitHub (usually referred to as the origin remote).Īlthough this may at first seem trickier than using a GitHub pull request as described in Option 2 below, we recommend this approach. You pull changes from that upstream remote into your local branch. This is usually referred to as the upstream remote. In this approach, you add the original Epic Games Unreal Engine repository to your local copy of your fork as a new remote repository.

This page describes two different approaches you can use to update a branch of your fork so that it matches the latest changes in the main Unreal Engine repository. You'll probably want to pick up these changes periodically: perhaps every time we publish a new official release, every month, or even every day. As we make changes in the source code and issue new official releases, we continuously update the various branches of the Unreal Engine GitHub repository. One of the biggest benefits of working from source is that you always have access to the very latest improvements and new features that our team adds to Unreal Engine.

Github desktop fork update