title: Why would I set another branch besides master to track origin/master in Git?
body: <p>This might be a dumb question, but I've been learning Git on <a href="https://learngitbranching.js.org/" rel="nofollow noreferrer">learngitbranching.js.org</a> and a lesson came up where they were talking about if it's possible to set another branch that's not master to track origin/master. As in:</p>
  
  <blockquote>
    <p>You can make any arbitrary branch track <code>o/master</code>, and if you do so,
    that branch will have the same implied push destination and merge
    target as <code>master</code>. This means you can run git push on a branch named
    <code>totallyNotMaster</code> and have your work pushed to the <code>master</code> branch on
    the remote!</p>
  </blockquote>
  
  <p>I just don't understand why I would do that? Is there any scenario where this would be practical/needed? Do you guys ever do this in your work?</p>