aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJosh Marshall <10360503+jmarsh411@users.noreply.github.com>2022-10-17 11:02:24 -0400
committerJosh Marshall <10360503+jmarsh411@users.noreply.github.com>2022-10-17 11:13:34 -0400
commitfee4d0f98e167e735499d158e4ab38cf2394b390 (patch)
tree88bdbd0d87f2f11c308c0d83e463221c185b58e7
parente5323759e387ba347a9d50f8b0ddd16502eb71d4 (diff)
downloadgitignore-fee4d0f98e167e735499d158e4ab38cf2394b390.tar.gz
gitignore-fee4d0f98e167e735499d158e4ab38cf2394b390.zip
ignore meta files of unity packages
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.
-rw-r--r--Unity.gitignore1
1 files changed, 1 insertions, 0 deletions
diff --git a/Unity.gitignore b/Unity.gitignore
index 58cbc825..3496b7cd 100644
--- a/Unity.gitignore
+++ b/Unity.gitignore
@@ -59,6 +59,7 @@ sysinfo.txt
*.apk
*.aab
*.unitypackage
+*.unitypackage.meta
*.app
# Crashlytics generated file