Skip to content
Latchkey

GitHub Actions "fatal: detached HEAD" after actions/checkout

By default actions/checkout checks out the exact commit that triggered the run, leaving HEAD detached. Commands that assume a current branch (push to HEAD, git symbolic-ref) then fail.

What this error means

A step that tries to commit/push or read the current branch fails because the repo is in detached-HEAD state, with "fatal: detached HEAD" or a push that has no upstream branch.

github-actions
fatal: You are not currently on a branch.
To push the history leading to the current (detached HEAD) state now, use git push origin HEAD:<name-of-remote-branch>

Diagnose it: print the context before you change anything

Most workflow-expression bugs are not syntax errors, they are an expression reading something that is empty. GitHub resolves a missing property to an empty string instead of failing the run, so a wrong reference looks like a logic bug rather than a mistake. Dump the contexts first and you will usually see the answer immediately.

.github/workflows/ci.yml
- name: Dump contexts
  run: |
    echo '--- github ---'   ; echo '${{ toJSON(github) }}'
    echo '--- needs ---'    ; echo '${{ toJSON(needs) }}'
    echo '--- steps ---'    ; echo '${{ toJSON(steps) }}'
    echo '--- matrix ---'   ; echo '${{ toJSON(matrix) }}'
    echo '--- inputs ---'   ; echo '${{ toJSON(inputs) }}'

Check the context is allowed where you used it

Contexts are not available everywhere. The same expression can be valid in a step if and invalid in a job if, which is why an expression that works in one workflow fails when moved.

Where you wrote itContexts available there
run-namegithub, inputs, vars
concurrencygithub, inputs, vars
Top-level envgithub, secrets, inputs, vars
jobs.<id>.ifgithub, needs, vars, inputs
jobs.<id>.steps.ifgithub, needs, strategy, matrix, job, runner, env, vars, steps, inputs
jobs.<id>.outputsFull access, including secrets
Reusable workflow outputsgithub, jobs, vars, inputs

Common causes

Default checkout detaches HEAD

checkout fetches and checks out the triggering SHA directly, so HEAD points at a commit rather than a branch ref.

Pushing without naming a branch

git push from detached HEAD has no current branch to map to a remote branch.

How to fix it

Check out a branch or push to an explicit ref

  1. Pass ref: with the branch name to checkout, or check it out after.
  2. When pushing, target HEAD:branch explicitly.
  3. Set fetch-depth: 0 if you also need full history.
.github/workflows/ci.yml
- uses: actions/checkout@v4
  with:
    ref: ${{ github.head_ref || github.ref_name }}
- run: git push origin HEAD:${{ github.ref_name }}

Catch it before it reaches CI

Every failure in this cluster is statically detectable. actionlint parses workflow expressions, checks context availability against the same rules above, and validates needs references, so these bugs never need to cost you a run.

Terminal
# one-off
docker run --rm -v "$(pwd):/repo" --workdir /repo rhysd/actionlint:latest -color

# as a job, before anything expensive runs
- uses: actions/checkout@v4
- run: |
    bash <(curl -s https://raw.githubusercontent.com/rhysd/actionlint/main/scripts/download-actionlint.bash)
    ./actionlint -color

How to prevent it

  • Decide explicitly whether you need a branch checkout vs a SHA.
  • Push to HEAD:<branch> when on detached HEAD.
  • Document that checkout detaches by default.

Frequently asked questions

What causes GitHub Actions "fatal: detached HEAD" after actions/checkout?
There are 2 common causes: default checkout detaches head and pushing without naming a branch. checkout fetches and checks out the triggering SHA directly, so HEAD points at a commit rather than a branch ref.
How do I fix GitHub Actions "fatal: detached HEAD" after actions/checkout?
Check out a branch or push to an explicit ref. Pass ref: with the branch name to checkout, or check it out after.
What does GitHub Actions "fatal: detached HEAD" after actions/checkout actually mean?
A step that tries to commit/push or read the current branch fails because the repo is in detached-HEAD state, with "fatal: detached HEAD" or a push that has no upstream branch.
How do I stop GitHub Actions "fatal: detached HEAD" after actions/checkout happening again?
Decide explicitly whether you need a branch checkout vs a SHA. The prevention section lists 3 changes that keep it from recurring.

Related guides

References

Not every red build is your code. Latchkey repairs the ones that are not, on the runner. Start free → 30-day trial · No credit card