How a detached node could merge into a git branch?

I am using GitKraken on Windows. While I was pulling remote branch into local, I saw this wired log graph, circled in the image. It looks like there’s a detached node, a node without parent, but it is able to merge with another branch…not sure what does this means, any idea?

enter image description here

  • How to delete a commit on a git remote?
  • VS2013 - GIT not working
  • How do I get Composer to download the latest commit in the master branch from GitHub for a package?
  • How can I get Emacs to revert all unchanged buffers when switching branches in git?
  • How to manage multiple projects in git with different emails?
  • Track local ignored files with Git
  • Update after @VonC’s comment

    In this image, the commit with hash prefix 52a66d2 is the problematic one, and it looks like it had a parent in this view.

    So maybe it is GitKraken‘s fault?

    enter image description here

  • How does git status work internally?
  • Commit to git with a different path?
  • Where does Git store files?
  • Is there a quick git command to see an old version of a file?
  • Git - fatal: unknown error occured while reading the configuration files
  • git clone with ssh issue
  • One Solution collect form web for “How a detached node could merge into a git branch?”

    I found out commit 52a66d2 is committed almost 3 hours earlier than its parent which commit 3058015

    That means 52a66d2 has a parent (3058015), and its parent link is shown.

    But the display order might not be topological (the parents are not always shown before the children) but using --date=relative.

    (see also git show-branch, which defines the two orders)

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