Attempting to interpret output of 'git log –graph'

I’ve done a 'git --reset hard origin/master' on a local branch so I’m expecting my local branch to match exactly to the remote one. However when I do a:

git log --graph --oneline --decorate --all

I get the following output at the top:

  • What git commit practice is better?
  • gitlab: PAM authentication issues
  • Appending a pattern to the default diff header pattern (diff.cpp.xfuncname)
  • Change Git Directory Setup VS Code
  • Merge conflicts ruin my commit message while squashing commits
  • git: setting a single tracking remote from a public repo
  • *   dfd9bc6 (refs/stash) On z_tmp2: tmp1
    | * 49f3b6f index on z_tmp2: 84e2002 localconfig
    * 84e2002 localconfig
    | * 1110f48 (origin/congo-3.1-stable) Boiler plate code to support

    Commits 84e2002, 49f3b6f and dfd9bc6 appear to be local work which I though would’ve been wiped out by the 'reset --hard', but apparently I’m missing something.

  • Capistrano stops at git:check
  • What does 'git log branchA branchB' do?
  • LibGitSharp: Checkout Remote Branch
  • Can't see remote branch
  • Git: Permission denied on file that was too big to stash
  • How to delete commits from commit history on GitHub?
  • One Solution collect form web for “Attempting to interpret output of 'git log –graph'”

    The reset does not wipe anything out, it only literally resets a branch to a different commit.

    As you can see in your log output, you still have a ref (refs/stash, your default stash) pointing to your old commits.

    If you do not need those commits any longer and want to make them disappear from the log, use

    git stash drop

    The actual deletion of the commits from the Git object store will happen with the next run of Git’s garbage collector, once the commits are no longer referenced. But unless you have disk space issues, you probably won’t have to worry about that.

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