My git branch is showing 'origin/master' and 'origin/HEAD' in Sourcetree and I don't know how to merge the two

I recently merged a branch I was working on with the ‘master’ branch. I must have (still kind of a git n00b) done something when pushing or pulling that created both an origin/master and an origin/HEAD branches. Unfortunately, I didn’t keep a record of what commands I ran that did this. Currently, my team has a bunch of code in their master copies that I’m not getting when I check out the project (even if I clone to a new location).

Here’s a screenshot of what Sourcetree is showing:

  • git: how do I find the common ancestor of two branches… that have already been merged
  • git cherry-pick not working
  • git how to switch branches without committing your changes
  • Should I delete a branch after merging it?
  • Git missing code after merge
  • TFS — Sustainability of Cascading Branches
  • 2 branches

    I really need to get this resolved so I can keep working so any help will be greatly appreciated.

  • Git: repo for multiple users on a server
  • How do I resolve this issue of preventing push to origin wrt. GitHub?
  • How to Run Terminal as Administrator on Mac Pro
  • Best Practice Laravel gitignore
  • Connecting to a TFS server closes a Git solution
  • Automatic checkout after push
  • 2 Solutions collect form web for “My git branch is showing 'origin/master' and 'origin/HEAD' in Sourcetree and I don't know how to merge the two”

    It is just a pointer to master, a symbolic link if you wish. You can safely delete it by doing the following in a terminal (or git bash/cygwin for windows users):

    1. navigate to your repository
    2. execute: git remote set-head origin -d

    now it should be gone:

    $ git branch -r
    origin/master
    

    The branches you see that begin with origin/ are so-called “remote-tracking braches”. They tell you the position of the branches in the repository origin the last time git fetched from that repository.

    It’s nothing to worry about – this is actually helpful information. If you think those branch positions are out of date, you can run:

    git fetch origin
    

    … to update them.

    In any repository, HEAD is special kind of ref (a “symref”) that represents the current branch (or current commit, if you’re not on a particular branch).


    You can see in the diagram that your master branch is actually one commit ahead of origin/master, so if your colleagues have been pushing to master in origin and you ran git fetch origin (or something equivalent) recently, you already have all their work. However, they will be missing out on your commit until you push that.

    You say:

    Currently, my team has a bunch of code in their master copies that I’m not getting when I check out the project (even if I clone to a new location).

    If that’s the case, they’re probably pushing to a different branch, a different repository, or they haven’t pushed their work at all.

    Git Baby is a git and github fan, let's start git clone.