2

I was about to check in some code to git hub using the UI client when I got some issue with a detached head. I am using the client, and I'm not familiar with the git shell. Before me, another developer checked in some code to the master, and afterwards I tried to check in my code, and got the issue.

It never happened before and I was able to always commit and sync changes. Then suddenly it came up when the other person committed changes before me. Besides new code, nothing else changed on my end.

Also, I have the below error.

Screenshot

Is there any simple, easy, quick way I can get rid of this detached head thing and get my code onto the main branch?

Zolt
  • 2,761
  • 8
  • 43
  • 60
  • 1
    please post output of `git branch` and `git status` – Binoy Babu Dec 03 '12 at 07:27
  • Possible duplicate of [Fix a Git detached head?](http://stackoverflow.com/q/10228760/456814). –  May 30 '14 at 05:25
  • Possibly related: [Why did my Git repo enter a detached HEAD state?](http://stackoverflow.com/q/3965676/456814). –  May 30 '14 at 05:27

1 Answers1

2

The OP Frank solved it the "quick" way:

because of time constraints I just saved my uncommitted work, re-cloned the project, and updated it after.

You seem to have two issues:

  • you are in a detached HEAD
  • you won't be able to push since somebody already pushed before you

In both cases, opening a shell is advisable.
And backup your git repo first, in order to start over if those solutions don't work.

For the detached HEAD, following "Git: How can I reconcile detached HEAD with master/origin?":

git checkout temp
git checkout -B master temp

For the push:

git pull --rebase
(the refresh your GitHub GUI and you should be able to push)

If you still have a "Failed to load commit history" error message, check the GitHub GUI log.

Community
  • 1
  • 1
VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
  • I tried all these options but still received errors. Unfortunately because of time constraints I just saved my uncommitted work, re-cloned the project, and updated it after. Thanks anyways for the help. – Zolt Dec 04 '12 at 03:05
  • @Frank ok. I have included your workaround in the answer for more visibility. – VonC Dec 04 '12 at 06:56