- Home /
Recurring .meta files in GIT
Hi,
This isn't a Unity-breaking problem, but I find it kind of annoying that: I don't know why, programs like SourceTree keeps showing certain files as Untracked, even though I include 'em on Commits. Those files are .meta files almost all the times. Of course you cannot do certain things, (Like switching branches) with Unstagged changes.
We are a group of 3 people and it happens to everyone of us every so often. Does somebody knows why this happens?
Thanks in advance
What do you mean by "I include 'em on Commits"? If you look back at one of those commits, does it show the file(s) as having been added to the repository?
It hasnt happen again, weirdly enough. But I have had a long period of time with this... like a good $$anonymous$$onth or two seeing this files ALWAYS untracked. It might have something to do with a Branch o an specific merge situation, I'll investigate further.
Thanks for the reply. Yes, I see them being added on commits from time to time.
I'm sorry, I've only ever used git from the command line or web interfaces like github/bitbucket (you're showing us SourceTree, I presume?), so I'm not sure how to interpret your screenshots. If a file is being committed and then is later found to be untracked (without having been explicitly made so), then that's a very weird thing that I've never encountered myself
I do have vague memories of seeing people reporting this kind of oddness, and it turning out to be caused by the kind of filesystem they're using, so perhaps that would be something to consider. Sorry but I don't think I've got anything more to offer here :(