The quasi-answer (workaround) to your question (I think) is that .. there is no such thing as an “inclusion” for this function. If it does not display correctly, as I have seen many times, then Xcode has a discussion-time mental gap. Most likely, this (Xcode) is about to collapse ... but if you just want to make a deal with him / seal a deal / get the horse out of this suffering, etc.
, and you should be able to view your versions of la Time Machine, as usual.
EDIT Ripley believes or not. I think I'm wrong!
Most likely your git build has become "f-ed up", somehow differently.
For me, no amount of commitment in the GitHub client for Mac will fix the situation (for some files) ... However, thanks to this tip , I suggest that Xcode forcing is “good, look at yourself in the mirror for a long time” using the “actual” Xcode File -> Source control => commit command File -> Source control => commit , it seems, returns the functionality of editing versions of problematic source files.
Alex gray
source share