Search Issue Tracker

Fixed in 2020.1.X



Found in






Issue ID




[VCS] Pulled empty folder .meta files are automatically deleted after pulling changes with Git

Version Control


How to reproduce:
- User 1 with an empty folder runs Unity which creates a .meta file.
- User 1 commits and pushes the .meta file.
- User 2 pulls, and gets the new .meta file.
- User 2 opens Unity, but since there is no corresponding folder for the .meta file, Unity deletes the .meta file.
- User 2 commits the deleted .meta file.
- User 1 pulls again, runs Unity, and since the empty folder still exists on their computer, the .meta file is created again.

Expected result: The empty folder is automatically created when pulling its .meta file or alternatively .meta files for empty folders can't be pushed at all
Actual result: The empty folder's .meta file is automatically deleted after pulling it with Git

Reproduced in: 2020.1.0a1, 2019.3.0a12, 2019.2.2f1, 2018.4.7f1, 2017.4.32f1

Note: This behaviour does not reproduce with Perforce, with Perforce the empty folder is automatically created when pulling its .meta file. The folder does not get created when reverting lone .meta files though.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.