What is the process for getting updates from GitHub?
A bit of a newbie question here, not much a programmer and I was wondering how the updating process goes.
When new source code is released do we just download it into a new fork/repository from Github and then rebuild that with the required dependencies? Or do the required dependencies get updated as well and updating will require starting from square 1?
And can we over-write older versions of the source code repositories (that we haven't made changes to), so we don't have needless clutter?
I checked the FAQ but couldn't see anything about an updating process. Will updating UE4 while working on a bigger project still maintain it, for safety I don't think I would update from a working version on a major project but just in case there's a vital bug fix it might be worth it.
The update process will be different depending on how you acquired the UnrealEngine repository.
If you cloned directly from EpicGames/UnrealEngine, you can simply update by pulling the latest commits:
And then checking out the version tag you're interested in:
If you forked, you will have a remote branch named
If you have not already done so, define a new remote branch pointing to Epic's UnrealEngine repo:
Now fetch the most up-to-date data from the
Once that completes, you're ready to merge in whichever version of the upstream branch that you want. To merge in the latest version 4.1 changes:
If any conflicts were encountered while merging, resolve them:
You then need to commit the new changes:
For more on working with forks, please refer to GitHub's documentation: https://help.github.com/articles/fork-a-repo
Required dependencies do not get updated automatically when you pull the latest changes from GitHub. It is likely that these zip files will change between releases, so you will need to manually download the latest versions and re-extract them into your local workspace.
You may safely overwrite old source repos, but in practice you shouldn't have to. When you pull the latest changes from GitHub, all local source code will be updated to the most recent version. The simplest workflow is to work from a single repo clone and do all updating in-place. You shouldn't need to generate multiple copies of your cloned repos unless you have a compelling reason to do so.
Given the manual nature of required binary zip files, you may accumulate some clutter in folders not governed by the repository (such as those created during zip file extraction), but it shouldn't be a major concern. We are hoping to improve this part of the process in the future.
answered Mar 31 '14 at 08:11 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here