Contents
What files should I Gitignore?
So that’s the general idea: your project (repository) . gitignore should list the names or name-patterns of files that will be found in work-trees when working with your project, but that should not be committed to the project. In other words, it’s not OS-specific, it’s project-specific.
Should I commit .meta files Unity?
No. Unity meta files contain valuable information about the assets in your project. You should add them to your git repository. See our how to add a Unity Project to GitHub article to learn what a .
Why we use git ignore file?
The git ignore file rule allows you to ignore a file you’ve committed in the past. You use it when you do not want to recommit a file, for example a build artifact.
Can you use git with Unity?
By default, the Unity editor does not work well with Git. To name a few problems: Noise: The editor manages hundreds of temporary files. Merely opening or closing the editor will create, delete, or modify some of these files.
Can I delete meta files?
meta files contain important information. png file. If you delete this . meta file, it will regenerate it, but you’ll lose any import settings you had set.
Should .gitignore be tracked?
Ignored files are tracked in a special file named . gitignore that is checked in at the root of your repository. There is no explicit git ignore command: instead the . gitignore file must be edited and committed by hand when you have new files that you wish to ignore. .
What should I exclude from my game’s source?
With the current version of Unity, just check in anything in the Assets folder and ProjectSettings folder. Don’t check in anything under Library, or at the top level. A good reference for this kind of lists is GitHub’s gitignore templates. The Unity-specific list is here.
Do you need to check generated files in source control?
Most would argue that you shouldn’t be checking generated object files and executables into source control. The same arguments apply to generated source. If you need to look at the historical version of a generated file you can sync to the historical version of its sources and rebuild.
What are the different types of source control?
Our systems support two types of source control: Git (distributed) and Team Foundation Version Control (TFVC). TFVC is a centralized, client-server system. In both Git and TFVC, you can check in files and organize files in folders, branches, and repositories.
How are generated source files and executables treated?
Generated source files are build artifacts just like object files, libraries and executables. They should be treated the same. Most would argue that you shouldn’t be checking generated object files and executables into source control. The same arguments apply to generated source.