Deploying to gh-pages from @ eab97b5 🚀

collaborating/sharing-a-branch/index.html

@@ -2000,7 +2000,7 @@ <h1 id="sharing-a-branch">Sharing a branch<a class="headerlink" href="#sharing-a
 </li>
 <li>
 <p>Push this branch to your remote repository:</p>
-<div class="highlight"><pre><span></span><code>git<span class="w"> </span>push<span class="w"> </span>-u<span class="w"> </span>origin
+<div class="highlight"><pre><span></span><code>git<span class="w"> </span>push<span class="w"> </span>-u<span class="w"> </span>origin<span class="w"> </span>collab/jamie
 </code></pre></div>
 </li>
 <li>

using-git/how-to-use-branches/index.html

@@ -2101,7 +2101,7 @@ <h2 id="creating-a-new-branch">Creating a new branch<a class="headerlink" href="
 git<span class="w"> </span>checkout<span class="w"> </span>-b<span class="w"> </span>my-new-branch<span class="w"> </span>my-other-branch<span class="w">  </span><span class="c1"># From an existing branch</span>
 </code></pre></div>
 <p>You can then create a corresponding <strong>upstream branch</strong> in your remote repository (in this example, called "origin") by running:</p>
-<div class="highlight"><pre><span></span><code>git<span class="w"> </span>push<span class="w"> </span>-u<span class="w"> </span>origin
+<div class="highlight"><pre><span></span><code>git<span class="w"> </span>push<span class="w"> </span>-u<span class="w"> </span>origin<span class="w"> </span>my-new-branch
 </code></pre></div>
 <h2 id="working-on-a-remote-branch">Working on a remote branch<a class="headerlink" href="#working-on-a-remote-branch" title="Permanent link">&para;</a></h2>
 <p>If there is a branch in your remote repository that you want to work on, you can make a local copy by running:</p>

using-git/pushing-and-pulling-commits/index.html

@@ -2049,7 +2049,11 @@ <h2 id="pushing-your-first-commit-to-a-remote-repository">Pushing your first com
 <p>This is a good time to create a <code>README.md</code> file and write a brief description of what this repository will contain.</p>
 </div>
 <p>Once you have at least one commit in your local repository, you can create a corresponding <strong>upstream branch</strong> in the remote repository with the following command:</p>
-<div class="highlight"><pre><span></span><code>git<span class="w"> </span>push<span class="w"> </span>-u<span class="w"> </span>origin
+<div class="highlight"><pre><span></span><code>git<span class="w"> </span>push<span class="w"> </span>-u<span class="w"> </span>origin<span class="w"> </span>&lt;branch-name&gt;
+</code></pre></div>
+<p>The default branch will probably be called <code>"main"</code> or <code>"master"</code>, depending on your <a href="../first-time-git-setup/">Git settings</a>.
+You can identify the branch name by running:</p>
+<div class="highlight"><pre><span></span><code>git<span class="w"> </span>branch
 </code></pre></div>
 <div class="admonition note">
 <p class="admonition-title">Note</p>
@@ -2063,7 +2067,7 @@ <h2 id="pushing-your-first-commit-to-a-remote-repository">Pushing your first com
 <p>and pull commits by running:</p>
 <div class="highlight"><pre><span></span><code>git<span class="w"> </span>pull
 </code></pre></div>
-<p>without having to specify the remote repository.</p>
+<p>without having to specify the remote repository or branch name.</p>
 <h2 id="forcing-updates-to-a-remote-repository">Forcing updates to a remote repository<a class="headerlink" href="#forcing-updates-to-a-remote-repository" title="Permanent link">&para;</a></h2>
 <p>By default, Git will refuse to push commits from a local branch to a remote branch if the remote branch contains any commits that are not in your local branch.
 This situation <strong>should not arise</strong> in general, and typically indicates that either someone else has pushed new commits to the remote branch (see the <a href="../../collaborating/">Collaborating</a> section) or that you have altered the history of your local branch.</p>