#Git switch branch detached head code#

Make sure you follow me on Twitter for more up-to-date news, articles and tips. If you find yourself in the detached HEAD state, remember that you can always preserve your changes by creating and checking out to a new branch, then committing and merging the changes in the desired branch. I hope you find these commands as useful as I did.

Git is amazing and I enjoy working with it more than any other source control solution ever.

#Git switch branch detached head code#

Once you’re happy with the changes, you then have the option to bring those changes to the main working branch using the following commands:Īnd with that, we fixed the problematic code while, at the same time, we avoided carrying over the bad commits. But since you’re not on a branch any more you’ve detached the HEAD. In Git, the HEAD always points to the tip of the current branch. However, if you decide to go with the first option, then you will be working with a detached HEAD. The new branch gives you a bit more flexibility. Another option is to create a totally new branch (a feature branch if you like): From that point on, you can continue working as normal. The command to do this is:Ĭ2744f95d is the commit hash (SHA) so make sure you find and use the right commit hash. Git allows you to do this by temporarily switching to a different commit. I normally work my way around git but this time its bugging me I am on a certain branch which had lets say 3 commits since its creation (i.e. I was aware that the last couple of check-ins were bad and I wanted to pick up and continue working from a known working point. I’ve recently had to use this awesome Git feature to fix a problem. Merge detached HEAD back to origin/master – Git 22 August 2015