title: Pushing code to multiple remotes
body: <p>I'm new to posting/commenting on StackOverflow so I couldn't comment in this link: <a href="https://stackoverflow.com/questions/14290113/git-pushing-code-to-two-remotes/14290145#14290145">Git - Pushing code to two remotes</a></p>
  
  <p>I noticed that the order of the push URLs matter. In the case of:</p>
  
  <pre><code>$ git remote show origin
  * remote origin
  Fetch URL: git://original/repo.git
  Push URL: git://another/repo.git
  Push URL: git://original/repo.git
  </code></pre>
  
  <p>It will push to <code>another</code> first. But if that <code>another</code> is inaccessible, the push will fail and git won't bother pushing to <code>original</code>. My workaround was to switch the Push URL manually in <code>.git/config</code> so that <code>original</code> comes first (assuming more accessible).</p>
  
  <p>Is this scheme reliable for working with multiple branches? I'm using <code>original</code> as my main for fetch/pull, and <code>another</code> for backup. Or will I be better off with using alternative methods (i.e. two remotes with two pushes)?</p>