I use perforce for version control of project files in combination with binary engine from launcher. I plan to move to github version of engine as I need to do changes in engine but I am not sure what is best way to track changes in engine source with ability to easily port everything to future engine versions.
I can think about some ways how to do that:
- Use Perforce for project files and GitHub for engine. Commit all engine changes to my github repo and then use git commands to move to newer version. This sounds nice but I am not sure if using two version control systems is really needed, especially when I can have only one enabled in Visual Studio plugins.
- Add engine files to my perforce depot. However, I am not sure how to not lose my changes when I will be downloading new engine version from github as git will not know about my changes because they will be uploaded to perforce only.
I am sure there are other, better ways too.
What are best practices and what do you suggest me ?