Unity packages were already ignored, but it seems in recent versions of Unity these also generate meta files for these. If the meta file isn't also ignored, the person who imports an asset containing a .unitypackage file could accidentally commit the meta files. For another who downloads those meta files, Unity would automatically delete them since they don't have the .unitypackage. The the importer commits them again and the cycle goes on and on until someone like me gets fed up.
This fixes that inconsistency by adding the *.unitypackage.meta to the ignore list.
If a user has ignored an asset (no matter how dubious that decision may be), they also want to ignore the .meta file. Instead of bringing back .metas that have been ignored, this template should trust that a user has ignored the files they want to ignore.
You'd encounter this issue if you had added an ignore for an asset and its meta above this Unity template, or if another template ignored an asset and meta.
In general excludes may be dangerous in these templates, as they can have unintended consequences on other templates.
* Added Addressables.
Prevent automatically generated addressable files to end up in Git.
* Update .gitignore to exclude packed Addressables and Android auto-generated files.
When a Unity project is opened in Jetbrains Rider, it installs a editor plugin into the Assets/Plugins/Editor/Jetbrains folder to manage Unity->Rider integration. This plugins life cycle is managed by your local Rider install and is automatically updated by Rider. It should not be committed to source control. This is documented by Jetbrains here https://www.jetbrains.com/help/rider/Unity.html
This change should ignore both the Jetbrains plugin folder and its .meta file correctly. For completeness, it would be nice to also ignore the /.idea*/ settings folder that Rider autogenerates, but i see a PR implementing that change has already been rejected.
* Added leading slashes to ignored directories so that valid subdirectories aren't ignored incorrectly
* Added comment to recommend .gitignore placement; added leading slash for AssetStoreTools rule
* Added a leading slash to never ignore .meta files in the root Asset folder
Only people building Unity plugins will need to import the asset store tools plugin into their project, and it's a toss up whether they want to commit the tooling into their repo (they might or they might not want to, it highly depends on their workflow). The default .gitignore shouldn't be making this choice for these users.
Unity projects targeting the 2.0/3.5 runtime or built with mono < v5.0 generate `mdb` files, not `pdb` files.
Looks like the `crashlytics-build.properties` gets around in more than just the `StreamingAssets` folder, looking at [examples around the internets](https://github.com/auth0/sharelock-android/blob/master/app/src/main/assets/crashlytics-build.properties), so it should probably just be ignored as a filename.
* Update Unity.gitignore
Prevents directories: `Library`
`Temp`
`Obj`
`Build`
`Builds`
`Assets/AssetStoreTools`
from being included in the remote if the project sits in the `Assets` folder.
* removed wildcards from Unity's .gitignore
Prevents directories: `Library`
`Temp`
`Obj`
`Build`
`Builds`
`Assets/AssetStoreTools`
from being included in the remote if the project sits in the `Assets` folder.
Since the version 5.2, Unity has used Visual Studio 2015 instead of MonoDevelop as default script editor in Windows.
This change may be helpful for Unity developers who use the recent version of Unity in Windows.
With the current setup these folders are ignored in the whole repo, but they're only automatically generated in the project root so it makes sense to only ignore the ones in the root.
I made this change because one of the assets in my project uses a folder called 'Library', and I was wondering why it never uploaded that folder.
By having the leading `/` infront of the `*` makes these types of files relative to the directory the gitignore is in. If you create a Unity project inside of a git directory Unity forces you to create a new directory, thus not picking up these files.
