The issue seems to be seen on the destination, that is the server side.
The OP don't see the modification on the server side either because because:
- the destination repo is non-bare (in which case the working tree isn't updated)
- the destination repo is bare (in which case there is no file to see since it is a repo without working tree)
That last case is usually completed by a post-receive hook in order to checkout that repo in a separate folder, in order to see what has just been pushed.