Please someone tell me I’m wrong, PLEASE! Because if this is the issue it has cost me 10s if not 100s of man hours in lost work trying to chase down why files fuck-up between Git pulls.
I have a file, we will call example.py which lives on my development VM. I access this file by mounting it’s folder as a disk using Transmit & sFTP. I edit the file and push it into our Git repo. A colleague then adds some lines to the file and I pull down his changes.
The next time I open the file it appears that Coda opens a cached version of the file!? I do not see the changes my colleague has made. So when I then edit and commit the file it wipes all his code! What. The. Fuck?
I’ve been noticing this happening a lot recently but had put it down to botched merges, but here is an example; I have a file models.py which at present in my master branch has 129 lines. When I SSH into the server I can check this;
Which matches what I see in Coda. However if I then checkout a previous version of the file (before Coda lost a bunch of changes) the line count changes;
If I close and reopen the file in Coda, the line count remains the same. The file has not changed!! If this is what is happening this is a HUGE flaw, rendering the editor completely worthless. I seriously hope that someone at @Panic can explain what is happening here?
Looks like it is not Coda, it’s Transmit. Same sickness, different disease, but the same carrier. Still on you @Panic. Why does it cache files like this? That is seriously broken.