moved git working copy, changes no longer detected -

So I made untold changes to my work copy. I got out of the disk space, so I moved the copy of the work into another section. Now GIT does not believe that there are changes to be committed. Not sure how I should solve this. Thank you.

OK, we have a brief summary of coming to mind with small information :

If you actually corrupt the clone by copying a part of it (why ever), then it is corrupt, there is no magic magic button, Can solve the data loss. But I suspect that this issue is here, your details are not fit, in this way someone has expected to complain to the guit or point to at least non-files or changed files. If I rightly tell your comments, instead git does not show any local modifications, so no one makes a claim.

Secondly, if some git actually lose some control over some files , Which is actually local modifications (which really means ...), one thing is that you can try to recover the least part of the changes: some other place to date Make another clone of any other place One repository (remember: it is not "server" in Jiaiti which serves as the central repository, not only clones at eye level). Now copy from your estimated broken clone to the latest file, but under GIT control, only those files, image files, images and so on are those files. If the difference in the new GIT clone should now show local modifications. You can get the same insights using just one diff tool to compare both clone files but again: I suspect that this is your problem

its Instead I have the impression that you have not really lost anything, but the situation is simply unknown. Two possible aspects came into mind:

1. Maybe you switch by mistake during or after this step, before switching to another branch? In that situation, you are now showing the status of that branch, and not before, if you then switch back to the previous branch then you will see your modifications again.

2. And this is actually my guess what happened here: all right, your local amendments have been made and committed to them, but you push them into any other repository Not given. In that situation, GIT does not really show any local amendments, there is no one but in that case your clone has a different log (history): it shows that it exists locally , But not in other clones (repositories). In that case, you have to do everything. If I read between those lines I say that you are using a centralized amendment control system such as Duplication or CVS, since then, when you are using your terminology ("copy of the work") Git is different from those people, there are different concepts that are actually confusing at first, when I was confused myself by switching ;-) But the gits approach makes a lot of sense. It provides full potential, features, flexibility and robustness, so investing in the switch is well worthwhile in my eyes.

   So, what is your position , check your branches, log off commits, and compare with other clones (repositories). I hope this is one of the last two aspects which I describe. In that case you have corrected everything, lost nothing and today the sun smiles to you: -)