Community Tutorial: Integrating engine source from GitHub to project's Perfoce repository

General Tutorial & Course Discussions
1

A lot of developers are afraid of using “source builds” - Unreal Engine compiled from the source by a team, opening doors to modifying the engine. One of the reasons is they see the process of integrating of new engine version as painful and time-consuming.

This tutorial describes the easy process of integrating engine changes via GitHub, where the engine source code is available for everyone. It leverages Git infrastructure to merge engine changes without much hassle.

https://dev.epicgames.com/community/learning/tutorials/oZ9d/unreal-engine-integrating-engine-source-from-github-to-project-s-perfoce-repository

1 Like
2

Read your tutorial and a question came to mind:
Does this procedure doubles version control?
What I understood was:

  1. Modify Engine sources
  2. Push on Github
  3. Reconcile on P4V (which would mean Submitting modifications on Perforce too)

So if I am correct what is the point of pushing on Github if you reconcile with p4v? Or maybe I am missing something.

3

It was my preferred way of handling merge conflicts. GitHub Desktop is simply throwing a nice list of all conflicts, which makes it easy to fix if one person can handle all conflicts.

Indeed, I should explain in the tutorial why I went this way. Thanks, I’ll think how to update the tutorial.