I was doing some work in my repository and noticed a file had local changes. I didn't want them anymore so I deleted the file, thinking I can just checkout a fresh copy. I wanted to do the Git equivalent of
svn up .
Using git pull didn't seem to work. Some random searching led me to a site where someone recommended doing
git checkout HEAD^ src/
(src is the directory containing the deleted file).
Now I find out I have a detached head. I have no idea what that is. How can I undo?
Detached head means you are no longer on a branch, you have checked out a single commit in the history (in this case the commit previous to HEAD, i.e. HEAD^).
git switch -c tmp - this will save your changes in a new branch called tmp.git switch mastermaster, run git merge tmp from the master branch. You should be on the master branch after running git switch master.You only need to checkout the branch you were on, e.g.
git switch master
Next time you have changed a file and want to restore it to the state it is in the index, don't delete the file first, just do
git restore -- path/to/foo
This will restore the file foo to the state it is in the index.
git checkout path/to/foo could conflict with git checkout some-branch, so it would be better to use git checkout -- path/to/foo to avoid these conflicts. –
Bolivar Previous HEAD position was 7426948... –
Wrongly git reflog –
Gervase git checkout master, Git advises you: Warning: you are leaving 1 commit behind, not connected to any of your branches [...] If you want to keep it by creating a new branch, this may be a good time to do so with: git branch <new-branch-name> <commit-hash>. I don't believe following this answer ipsis litteris causes lose of work. But in any situation, a backup is always a good precaution. –
Logic master and you may delete the tmp local branch: git branch -d tmp –
Logic git merge <commit has> directly. I don't know why you'd want to create a branch here. –
Garwin git branch -a, then checked out one of those branches and I'm in a 'detached HEAD' state. There are no changes associated with the detached HEAD state. The checkout worked fine and all my files match what was in that commit. –
Emmie git:(2020_04_21) git checkout origin/2020_05_05 Note: checking out 'origin/2020_05_05'. You are in 'detached HEAD' state. Yeah maybe a little bit, kind of, maybe random? –
Simdars origin/2020_05_05 is a remote branch, which can't be checked out directly. If you're not sure why that is, consider that you don't actually control a remote branch, as it's on a different computer -- so you can't commit to or edit it without a network connection, and Git only requires a network connection on fetch/push/pull operations. Instead you have to make the changes on a local branch and then push them. You probably wanted just git checkout 2020_05_05, which will create a local branch (which you can edit) that tracks the remote branch. –
Polak git reset --hard tmp instead of git merge tmp, to not clutter the git commit history. –
Uncurl git checkout main I found 'main' name on git reflog: "789456 (HEAD -> , , main) –
Myasthenia If you have changed files you don't want to lose, you can push them. I have committed them in the detached mode and after that you can move to a temporary branch to integrate later in master.
git commit -m "....."
git branch my-temporary-work
git checkout master
git merge my-temporary-work
Extracted from:
git stash ? As that is the first thing that comes to my mind. creating a new branch will be an overkill. –
Sanitary git rebase my-temporary-work and then delete the branch git branch -d my-temporary-work so it appears as if you committed to the right branch in the first place. –
Blen git stash does sound like the perfect tool for this case. Could you please write an answer with the suggested steps to achieve that? –
Blen git branch .. with git stash and git merge .. with git stash apply. –
Led $git reflog (look for the SHA of the HEAD you want to restore) . $git checkout HEAD_SHA (you should on this detached head now) . $git branch BRANCH_NAME (you merge change from HEAD to a new branch by doing this) . Then with this new branch you can merge, rebase, cherry-pick do whatever you'd like to –
Ain git checkout <headless-state>. This will save the detached head to this branch. 2. Check into a branch which is tracking an origin head correctly git checkout <branch-name-to-attach-headless> this is any branch of your choice, including main (master). 3. In this branch merge git merge <headless-state> the detached head now tracks the branch you have switched to. If you don't want changes delete git delete <headless-state> this is a destructive command.More –
Siliqua How to exit (“fix”) detached HEAD state when you already changed something in this mode and, optionally, want to save your changes:
Commit changes you want to keep. If you want to take over any of the changes you made in detached HEAD state, commit them. For example:
git commit -a -m "your commit message"
Discard changes you do not want to keep. The hard reset will discard any uncommitted changes that you made in detached HEAD state:
git reset --hard
(Without this, step 3 would fail, complaining about modified uncommitted files in the detached HEAD.)
Check out your branch. Exit detached HEAD state by checking out the branch you worked on before, for example:
git checkout master
Take over your commits. You can now take over the commits you made in detached HEAD state by cherry-picking, as shown in my answer to another question.
git reflog
git cherry-pick <hash1> <hash2> <hash3> ...
git reset --hard was exactly was I needed, because I want the upstream to be the source and the local changes should be removed. –
Amplitude HEAD is a pointer, and it points — directly or indirectly — to a particular commit:
Attached HEAD means that it is attached to some branch (i.e. it points to a branch).
Detached HEAD means that it is not attached to any branch, i.e. it points directly to some commit.
In other words:
To better understand situations with attached / detached HEAD, let's show the steps leading to the quadruplet of pictures above.
We begin with the same state of the repository (pictures in all quadrants are the same):
Now we want to perform git checkout — with different targets in the individual pictures (commands on top of them are dimmed to emphasize that we are only going to apply those commands):
This is the situation after performing those commands:
As you can see, the HEAD points to the target of the git checkout command — to a branch (first 3 images of the quadruplet), or (directly) to a commit (the last image of the quadruplet).
The content of the working directory is changed, too, to be in accordance with the appropriate commit (snapshot), i.e. with the commit pointed (directly or indirectly) by the HEAD.
So now we are in the same situation as in the start of this answer:
git reset --soft <commit> moves the current branch head (HEAD) to <commit>. How come that git reset does not end up in a detached state then although HEAD points to a commit (as the documentation claims)? There must be more to it, as can be seen by looking at .git/HEAD. –
Thames Detached head means:
If you have no changes: you can switch to master by applying the following command
git checkout master
If you have changes that you want to keep:
In case of a detached HEAD, commits work like normal, except no named branch gets updated. To get master branch updated with your committed changes, make a temporary branch where you are (this way the temporary branch will have all the committed changes you have made in the detached HEAD), then switch to the master branch and merge the temporary branch with the master.
git branch temp
git checkout master
git merge temp
If you made changes and then realized that you are on a detached head, you can do: stash -> checkout master -> stash pop:
git stash
git checkout master # Fix the detached head state
git stash pop # Or for extra safety use 'stash apply' then later
# after fixing everything do 'stash drop'
You will have your uncommited changes and normal "attached" HEAD, like nothing happened.
Here's what I just did after I realized I was on a detached head and had already made some changes.
I committed the changes.
$ git commit -m "..."
[detached HEAD 1fe56ad] ...
I remembered the hash (1fe56ad) of the commit. Then I checked out the branch I should have been on.
$ git checkout master
Switched to branch 'master'
Finally I applied the changes of the commit to the branch.
$ git cherry-pick 1fe56ad
[master 0b05f1e] ...
I think this is a bit easier than creating a temporary branch.
git cherry-pick <hash>. –
Muley When you check out a specific commit in git, you end up in a detached head state...that is, your working copy no longer reflects the state of a named reference (like "master"). This is useful for examining the past state of the repository, but not what you want if you're actually trying to revert changes.
If you have made changes to a particular file and you simply want to discard them, you can use the checkout command like this:
git checkout myfile
This will discard any uncommitted changes and revert the file to whatever state it has in the head of your current branch. If you want to discard changes that you have already committed, you may want to use the reset command. For example, this will reset the repository to the state of the previous commit, discarding any subsequent changes:
git reset --hard HEAD^
However, if you are sharing the repository with other people, a git reset can be disruptive (because it erases a portion of the repository history). If you have already shared changes with other people, you generally want to look at git revert instead, which generates an "anticommit" -- that is, it creates a new commit that "undoes" the changes in question.
The Git Book has more details.
git checkout path/to/foo could conflict with git checkout some-branch, so it would be better to use git checkout -- path/to/foo to avoid these conflicts. –
Bolivar Since "detached head state" has you on a temp branch, just use git checkout - which puts you on the last branch you were on.
git reflog and can be taken over into a new branch or via git cherry-pick into an existing branch. See this question. –
Harass you probably did git reset --hard origin/your-branch.
Try to just git checkout your-branch
Being in "detached head" means that HEAD refers to a specific unnamed commit (as opposite to a named branch) (cf: https://git-scm.com/docs/git-checkout section Detached head). In reality, this means that you have checked out a commit but there is no branch name associated with it.
You may choose to only create a new branch associated with your commit by
git branch new-branch-name.
This allows you to save your current state in a new branch named new-branch-name and not be in a detached head state anymore.
Or if you would like to come back to the previous state, you need to select the branch that was selected before by
git checkout @{-1}
To further clarify @Philippe Gerber's answer, here it is:
Before cherry-pick, a git checkout master is necessary in this case. Furthermore, it is only needed with a commit in detached head.
Addendum
If the branch to which you wish to return was the last checkout that you had made, you can simply use checkout @{-1}. This will take you back to your previous checkout.
Further, you can alias this command with, for example, git global --config alias.prev so that you just need to type git prev to toggle back to the previous checkout.
Detached head means you have not checked out your branch properly or you have just checked out a single commit.
If you encounter such an issue then first stash your local changes so that you won't lose your changes.
After that... checkout your desired branch using the command:
Let's say you want branch MyOriginalBranch:
git checkout -b someName origin/MyOriginalBranch
To add to @ralphtheninja's answer. If you get this message after using git checkout master:
Please commit your changes or stash them before you switch branches. Aborting
Then you can simply force the checkout using the -f flag as follows:
git checkout -f master
Apparently this will result in losing all the changes made in the detached mode. So be careful when using it.
This approach will potentially discard part of the commit history, but it is easier in case the merge of the old master branch and the current status is tricky, or you simply do not mind losing part of the commit history.
To simply keep things as currently are, without merging, turning the current detached HEAD into the master branch:
detached-head) that will contain the files in their current status:git checkout -b detached-head
git branch -D master
git branch -M master old-master
git branch -M detached-head master
Credit: adapted from this Medium article by Gary Lai.
I was in a similar situation.
For some reason I ended up with a detached head - I had made commits on the same path as the branch I thought I was on - eg HEAD was a child of the branch tag but for some reason the branch tag had stayed back at a historic commit... possibly because I had pushed??
It wouldn't let me push because I wasn't considered to be on the branch I thought I was on.
I didn't want to change any of my history or do any cherry picking and I'd just spent about 8 weeks working on the branch so reset --hard was making me a bit nervous!
The solution was just to do the following:
git branch -f myStuckBranch HEAD
git checkout myStuckBranch
You need to do the checkout even though HEAD and myStuckBranch are now pointing at the same thing because you are still considered to be in the detached head state (not on a branch)
I'm not an expert with git (having mostly used mercurial which would never create this weird situation) but my understanding of this command is that it just says "change myStuckBranch to point at HEAD".
I routinely find myself using this command to merge in changes from master after fetching without having to swap my working directory - otherwise it tries to use the old (uninteresting) version of master:
git fetch
git branch -f master origin/master -- err yeah don't just ignore what's been going on remotely - eg point my master at the real master
git merge master -- merge the changes into my local branch
It's a bit annoying to have to manually have to do that all the time but still better than having to change your working directory just to update another branch in order to merge in changes from it.
master locally—git pull already does git fetch and git merge for you. No point in making things pointlessly more complicated (though it is always nice to have an understanding of what is going on)! –
Boltonia git checkout -B myStuckBranch –
Internment git pull origin master. That will not update your local repository’s master branch, but it will fetch and then merge origin/master into the current branch. You could also do git fetch; git merge origin/master (which does not update your local master branch). Or even git fetch origin master:master; git merge master (which updates your local master branch like your snippet does but requires more typing). Again, it’s more important to do what you understand! –
Boltonia git pull one before, so many different ways of doing things! I just have the fetch/branch update as a bash function so it doesn't bother me any more. I think if you do the git merge origin/master it gives a less nice commit message –
Internment Git told me how to do it.
if you typed:
git checkout <some-commit_number>
Save the status
git add .
git commit -m "some message"
Then:
git push origin HEAD:<name-of-remote-branch>
Time to time Git shows :
To push the history leading to the current (detached HEAD) state now, use
git push origin HEAD:<name-of-remote-branch>
It means :
To fix that run 2 commands :
Normally HEAD points to a branch. When it is not pointing to a branch instead when it points to a commit hash like 69e51 it means you have a detached HEAD. You need to point it two a branch to fix the issue. You can do two things to fix it.
hashHEAD must point to a branch, not a commit hash is the golden rule.
This was a confusing thing to me when I started to work with git and later I figure out why this is happening and what is the best way to deal with such a situation.
The root cause for such occurrence is that normally git HEAD is always pointing to some branch and when you try to point the HEAD to some specific commit, you put HEAD into a detached HEAD state.
When HEAD is attached state -
cat .git/HEAD # output--> ref: refs/heads/master or ref: refs/heads/main
When HEAD is detached state -
cat .git/HEAD # output--> b96660a90cad75867453ebe1b8d11754bbb68b0e <commit hash>
Solution -
git stash # Temporarily shelves (or stashes) changes
git branch # Find your default branch
git switch master # Point HEAD to master or main branch
git stash pop # Apply all the changes you had previously
I wanted to keep my changes so, I just fix this doing...
git add .
git commit -m "Title" -m "Description"
(so i have a commit now example: 123abc)
git checkout YOURCURRENTBRANCH
git merge 123abc
git push TOYOURCURRENTBRANCH
that work for me
When you're in a detached head situation and created new files, first make sure that these new files are added to the index, for example with:
git add .
But if you've only changed or deleted existing files, you can add (-a) and commit with a message (-m) at the the same time via:
git commit -a -m "my adjustment message"
Then you can simply create a new branch with your current state with:
git checkout -b new_branch_name
You'll have a new branch and all your adjustments will be there in that new branch. You can then continue to push to the remote and/or checkout/pull/merge as you please.
Realizing I had a detached head without knowing how I managed to get it (like three commits away), I also found out that trying to merge, rebase or cherry-pick triggered hundreds of merge-conflicts, so I took a different approach:
(Assuming everything is committed (working tree is "clean"))
Save my commit messages: git log > /tmp/log
Save my working tree: mkdir /tmp/backup && cp -a all_my files_and_directories /tmp/backup
Revert to master: git checkout master
Remove all the working files and directories: rm ...
Use the backup: cp -a /tmp/backup/. .
git add and git commit using messages from saved /tmp/log, maybe repeating it with different sub-sets of files...
The disadvantage is that you loose your commit history if one file was changed multiple times since master, but in the end I had a clean master.
The detached HEAD means that you are currently not on any branch. If you want to KEEP your current changes and simply create a new branch, this is what you do:
git commit -m "your commit message"
git checkout -b new_branch
Afterwards, you potentially want to merge this new branch with other branches. Always helpful is the git "a dog" command:
git log --all --decorate --oneline --graph
If you hate head and wanna go back to main instead:
git checkout main
If you love head but just wish main tracked it:
git checkout -B main HEAD
(This works with any branch name, not just main, and for any commit pointer, not just HEAD.)
(If you have uncommitted changes that you want to commit, commit them first.)
I came here because I had the HEAD detached at... message.
In my case it wasn't due to some local changes because, on that system I never do any changes.
The reason for my message was: I accidently checked out origin/myBranch instead of myBranch.
So when checking out myBranch everything returned to normal.
This works for me, It will assign a new branch for detached head :
git checkout new_branch_name detached_head_garbage_name
With git rebase you can move your HEAD to the desired commit
Suppose you have your branch in a detached state, like this:
* bfcb8f9 Commit 4
* 540a123 Commit 3
* 4356d64 Commit 2
| * fecb8d2 Commit 2
|/
| * 8012f45 Commit 2x
|/
| * 6676d15 (HEAD -> master) Commit 2 --amend
|/
* 1818f91 Commit 1
The detached head was created by rebasing by mistake, pointing to a detached commit, which was created previously due a git commit --amend command.
If you want to move your HEAD ref to the most recent commit, apply a rebase with the desired HASH commit you want to point to. In this example, the hash is of the most recent commit:
git rebase bfcb8f9
and this will leave your branch with its HEAD poiting to the desired commit (the most recent in this case):
* bfcb8f9 (HEAD -> master) Commit 4
* 540a123 Commit 3
* 4356d64 Commit 2 --amend
| * fecb8d2 Commit 2
|/
| * 8012f45 Commit 2x
|/
| * 6676d15 Commit 2
|/
* 1818f91 Commit 1
First we need to understand
If it points to a commit directly, the HEAD is detached.
If it points to a commit indirectly, (i.e. it points to a branch, which in turn points to a commit), the HEAD is attached.
So if you want to attach HEAD to branch then we need to checkout branch
git checkout new_branch_name detached_head_garbage_name
git checkout is obsolete. Use git switch –
Tyburn git pull origin master
worked for me. It was just about giving remote and branch name explicitly.
pull command. –
Runnel © 2022 - 2024 — McMap. All rights reserved.
git checkout masterwill get you back on the master branch. If you wanted to clear out any working copy changes, you probably wanted to dogit reset --hard. – Weatherwisegit checkout -- src/– Sanitarycreate temp branch - checkout temp branch - checkout master - delete temp branch– Rozalinworking copy changes? Are you referring to the changes you made to files after checking out another commit (i.e., the changes you made while in a detached head state)? – Epilepticgit checkout master– Baccaratmaininstead ofmaster, usegit checkout mainto get back to it latest commit on that branch. – Epos