How to Fix Detached HEAD in Git Quickly and Easily

A detached HEAD in Git happens when you check out a commit directly instead of a branch. To fix it, create a new branch from the detached state using git switch -c <branch-name> or return to an existing branch with git switch <branch-name>.

Why This Happens

A detached HEAD occurs when you check out a specific commit instead of a branch. This means Git points to a commit directly, not to a branch name. Any changes made here are not saved to a branch and can be lost if you switch away.

bash

git checkout 1a2b3c4d5e6f7g8h9i0j

Output

Note: switching to '1a2b3c4d5e6f7g8h9i0j'.

You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, but
when you switch back to a branch, you will lose these commits unless you create a new branch.

The Fix

To save your work and fix the detached HEAD, create a new branch from the current commit or switch back to an existing branch. This attaches HEAD to a branch and keeps your changes safe.

bash

git switch -c my-new-branch

Output

Switched to a new branch 'my-new-branch'

Prevention

Always check out branches instead of commits directly. Use git switch <branch-name> to move between branches. If you want to explore a commit, create a branch first to avoid losing work.

Regularly commit your changes and push branches to remote repositories to keep your work safe.

Related Errors

Other common Git errors include:

• Unmerged paths: Happens during conflicts; fix by resolving conflicts and committing.
• Detached HEAD with lost commits: Use git reflog to find lost commits and recover them.

Key Takeaways

A detached HEAD means Git points to a commit, not a branch.

Fix it by creating a new branch with 'git switch -c '.

Avoid detached HEAD by always switching to branches, not commits.

Use 'git reflog' to recover lost commits from detached HEAD states.

Commit and push regularly to keep your work safe.