vurbid.blogg.se

Unity cloud build export project version
Unity cloud build export project version





unity cloud build export project version

Add and check the file in, every member of your team will get it the next time they update their workspaces. There are two different ways to share the nf with your coworkers, using Plastic SCM for it, of course. The definitive nf file #Common directories Otherwise, your coworkers will not be able to open the Unity project. Keep them always added to your Plastic SCM repository. Unity recommends never to exclude the Assets and the Project setting directories. They can hold thousands of files and weight several GBs, and if you delete them, Unity creates them again. The rule of thumb is to exclude all the directories and files that Unity regenerate automatically.įor example, Library and Temp directories are the most populated paths in your Unity project. If they are part of the repository, the users will face merge conflicts every time the IDE changes them locally.Įvery Unity project is different, but several paths are always part of the Unity project skeleton.

  • Avoid constant conflicts: Automatic files created by IDEs are changed continuously.
  • Smaller repository: Big assets are kept local therefore, the repository size doesn't grow.
  • The nf file contains a list of rules that makes those files and directories not to be tracked by Plastic SCM.

    unity cloud build export project version

    Unity, like many other editors such as Visual Studio and Visual Studio Code, and many others, creates a wide variety of files that shouldn't be part of the repository.







    Unity cloud build export project version