How to fix fatal: Cannot switch branch to a non-commit in Git

# For a local branch
git checkout refs/heads/<branch-name>

# For a remote tracking branch
git checkout refs/remotes/origin/<branch-name>

# This puts you in detached HEAD state
# Then create a local branch if needed:
git checkout -b <branch-name>

# Instead of:
git checkout feature-123

# Use:
git checkout refs/heads/feature-123

# Or for remote:
git checkout refs/remotes/origin/feature-123
git checkout -b feature-123

# Fetch latest from remote first
git fetch origin

# Checkout with explicit tracking
git checkout --track origin/<branch-name>

# Or use the -b flag to create a local branch
git checkout -b <branch-name> --track origin/<branch-name>

# Git switch handles this more gracefully
git switch <branch-name>

# Or explicitly create and track
git switch -c <branch-name> --track origin/<branch-name>

# Check what type of object your reference points to
git cat-file -t <name>

# See all references matching the name
git show-ref <name>

# Check if there's a conflicting tag
git tag -l | grep <name>

# Examine what the tag points to
git rev-parse --verify tags/<name>

# Delete the conflicting tag
git tag -d <tag-name>

# If it's on the remote too
git push origin --delete <tag-name>

# Now checkout should work
git checkout <branch-name>

# This shows commit, tree, blob, or tag
git cat-file -t refs/tags/<name>
git cat-file -t refs/heads/<name>

# Fetch all branches from all remotes
git fetch --all

# Fetch from specific remote
git fetch origin

# See all available branches now
git branch -a

# Check if your branch is listed
git branch -a | grep <branch-name>

# Standard checkout
git checkout <branch-name>

# If still failing, use explicit remote reference
git checkout -b <branch-name> origin/<branch-name>

# If you did a shallow clone, you may need to unshallow
git fetch --unshallow

# Then fetch all branches
git fetch --all

# See what Git resolves the reference to
git rev-parse <name>

# Get the full symbolic reference
git rev-parse --symbolic-full-name <name>

# Check if it's a valid commit
git rev-parse --verify <name>^{commit}

# See all matching references
git for-each-ref --format='%(refname) %(objecttype) %(objectname)' | grep <name>

# This shows "tree" instead of "commit"
git cat-file -t $(git rev-parse <name>)

# Find the commit that contains this tree
git log --all --full-history -- $(git rev-parse <name>)

# If your branch is named "12382", Git might think it's a commit hash
# Always use explicit reference paths for numeric names:
git checkout refs/heads/12382

# Or prefix with origin for remote branches
git checkout -b 12382 origin/12382

# Instead of:
git checkout -b 12382

# Use a descriptive prefix:
git checkout -b issue-12382
git checkout -b feature/12382
git checkout -b ticket-12382

# Always use refs/heads/ prefix
git checkout refs/heads/12382

# Or use -- to separate branch from paths
git checkout -- 12382

# Switch to an existing branch
git switch <branch-name>

# Create and switch to new branch
git switch -c <new-branch>

# Create branch tracking remote
git switch -c <branch-name> --track origin/<branch-name>

# Switch to a detached HEAD at a commit
git switch --detach <commit-hash>

# The error message may be more descriptive
git switch feature-123
# fatal: invalid reference: feature-123

# Check what references exist
git show-ref | grep feature-123

# Find the commit the branch should point to
git log --all --oneline | head -20
git log origin/<branch-name> --oneline -5

# Delete the problematic local branch
git branch -D <branch-name>

# Recreate from the correct commit
git branch <branch-name> <commit-hash>
git checkout <branch-name>

# Or recreate from remote
git checkout -b <branch-name> origin/<branch-name>

# Verify it exists on remote
git ls-remote origin | grep <branch-name>

# Fetch and create local tracking branch
git fetch origin <branch-name>:<branch-name>
git checkout <branch-name>