Setting up source control for a HoloLens Unity project

Jimmy Engström


Setting up source control for a HoloLens Unity project

Don't source control generated files

When source controlling your Unity HoloLens project there is no reason to save the generated code since it is generated =)
Unity won't replace some of the generated files so if you for example change icons/tiles in the Unity project, those part will not be replaced when generating the code again.
A good practice is to export to new folders every time.


There are only a couple of folders worth adding to source control.
When setting up your project for the first time, just add the .gitignore file from here:
That way only the important files will be controlled.
You can also do this when creating a new project on GitHub.

Setting up your project

Go to Edit -> Project Settings -> Editor
To make source control work hassle free, you should make sure version control has visible meta files (or hidden meta files, if you don't want to see them in Windows Explorer).
It will add a meta file for each asset in you project, this will make sure that only the asset and the meta files gets tagged as changed if you change an asset, otherwise the whole folder would be tagged as changed.
Also make sure Asset serialization -> Mode is set to "Force Text" this will make your source control handle diffs (text is easier to handle than binary-files.
Using the Hololens toolkit will change these settings for you.

Posted in HoloLens with : HoloLens