We are two games designers who want to work on the same Unity file, each editing code and art work. Here I am going to explain how we set up an environment to do this:
Following this tutorial we set up our first source controlled repository.
This means that all our source code is stored in the cloud so that both us can access it at any time. It also has a version history, so that we can rewind time if things break and see who has worked on things when.
Bitbucket is free for 5 or less users letting us keep all the code private, we could also have stored the information publicly on github – but seeing as the tutorial was good for bitbucket it seemed a shame not to use it.
The tutorial shows you how to use SourceTree which is a graphical representation of using Git through Terminal. By using SourceTree it makes the process a little more apparent for first time source control users.
Inviting your team member(s) to your bitbucket project. They will receive an email that allows them to access the code.
Clone the repository using SourceTree onto the other persons computer. Choosing a folder to put the code into on their desktop.
Check everything in SourceTree. They might need to pull the code.
They can then open the unity project and check it is working
If they make a change in Unity, save and then go back to SourceTree. They should now have files that need to be staged -> committed -> pushed.
For more information on the process check out this tutorial.
You do not need to stage any: Library or Temp files.
You can now go back to your computer and check SourceTree and if you need to pull any of their files. For further reading on source code control check out the Git Documentation.
You have now set up a collaborative unity environment where you can share information between a small team!