Clever Geek Handbook

After an apparently successful git push, the file misses the target

I am installing git between two AWS instances (call them A and B). I can extract the fine from A and see the changes in those files on B.

If I create a new file on B and commit it when I push from B to A, everything seems to be going well (I get a git message about creating objects ...), but I can't see the files on machine A. On machine A git status indicates that these files have been removed.

Why do I never see pushed files and why does git think they have been deleted?

+2


source to share


3 answers


See question Why can't I see changes in the remote repo after "git push"? For more information, see the Unexpected Behavior section of the GitFaq page on the Git Wiki.



+5


source


Move your working directory forward by A. Clicking is like fetching backward, not pulling backward. This does not affect the working directory.

git checkout $YOUR_BRANCH


Do this on machine A after pressing B.

+6


source


If it was obviously successful, then it would be obvious that there was a success. However, it looks like you are apparently in trouble.

-1


source






More articles:


All Articles