Add Unity generated meta file for an already ignored debugging file #2486
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reasons for making this change:
Unity generates and manages it's own
*.*.metametatdata files for every file and directory in a Unity project. These files must be added/removed/renamed along with their respective file/directory.*.pdbfiles (generated by Visual Studio for debugging in Windows) were ignored in #2240, but this did not include their corresponding*.pdb.metafiles.Similarly,
*.pidband their corresponding*.pidb.metafiles were ignored in #1319.Without this, Unity will complain that
*.pdb.metafiles exist when a corresponding*.pdbdoes not exist and remove the offending*.pdb.metafiles anyways. Committing these removals will cause them to be re-generated on the developers machine who has the*.pdbfiles. This causes unnecessary add/remove fighting in the codebase.Links to documentation supporting these rule changes:
Visual Studio
*.pdbdebugging filesUnity
*.*.metametadata filesUnity
*.*.metametadata files with respect to Version Control