title: Does pushing to the current branch of a remote repository update the remote's working directory?
body: <p>Assume the remote repository in the following has a working directory, so it also has a current branch.</p>
  
  <ol>
  <li><p>Is it correct that </p>
  
  <ul>
  <li><code>git push</code> can push to <strong>the current branch in a remote repository</strong>, and</li>
  <li>when that happens, <code>git push</code> doesn't update <strong>the working directory of the remote repository</strong>? </li>
  </ul>
  
  <p>I get the idea from Version Control with Git, by Loeliger, 2ed,
  especially the text in bold:</p>
  
  <blockquote>
    <p>Recall that the <strong>git push command does not check out files in the receiving repository.</strong> It simply transfers objects from the source
    repository to the receiving repository and then updates the
    corresponding refs on the receiving end.</p>
    
    <p>In a bare repository, this behavior is all that can be expected, because there is no working directory  that  might  be  updated  by 
    checked  out  files.  That’s  good.  However,  in  a development
    repository that is the recipient of a push operation, it can later
    cause confusion to anyone using the development repository.</p>
    
    <p><strong>The push operation can update the repository state, including the HEAD
    commit.</strong> That is, even though the developer at the remote end has done
    nothing, the branch refs and HEAD might change, becoming out of sync
    with the checked out files and index.</p>
    
    <p><strong>A developer who is actively working in a repository into which an
    asynchronous push happens will not see the push.</strong> But a subsequent
    commit by that developer will occur on an unexpected HEAD, creating an
    odd history. A forced push will lose pushed commits from the other
    developer. The developer at that repository also may find herself
    unable to reconcile her history with either an upstream repository or
    a downstream clone because they are no longer simple fast-forwards as
    they should be. And she won’t know why: the repository has silently
    changed out from underneath her. Cats and dogs will live together.
    It’ll be bad.</p>
  </blockquote></li>
  <li>If the idea that I get is correct, is <code>git push</code> the only git command
  that doesn't update the working directory when making change to the
  current branch of the same repository? What are other similar git commands? (To me, the other commands
  that make change to the current branch will update the working
  directory of the same repository.)</li>
  </ol>