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

  • When cloning git repo under Windows I get “error: unable to create file <file>… (Is a directory)”
  • Equivalent of the clearcase baseline and clearcase activities in Git?
  • Why does git pull --rebase fail when replaying existing commits?
  • Teamcity trigger builds for github pull-requests
  • How to patch code in someone else's project hosted on github
  • Am I looking at GIT branches in GIT clients wrong?
  • 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

  • Unable to install the latest release candidate of a Python library on GitHub
  • Why is git creating read-only (444) files?
  • What is the safest way to get rid of dangling blobs
  • Git stash single untracked file?
  • Deploying to website with Git remotes, but without post-receive hook
  • Does Git Add have a verbose switch
  • 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.