Home > Git > Git Reset Cheat Sheet

Git Reset Cheat Sheet

Move HEAD and unstage or discard changes safely when you need to rewrite local history.

What this cheat sheet is for

This git reset reference helps you complete common developer tasks quickly and avoid repeated trial-and-error when working under deadlines.

  • When you need a reliable command or pattern during debugging and incident response.
  • When you are implementing a feature and want a known-good syntax example immediately.
  • When onboarding teammates and documenting repeatable workflows for daily use.
  • When reviewing pull requests and verifying that command usage follows best practices.
  • Unstage files without losing edits.
  • Drop local commits before pushing.
  • Hard reset a broken branch to a known commit.

Modes and behavior

Show the three reset modes

git reset --soft HEAD~1

Example:

git reset --mixed HEAD~1

Discard staged and working tree changes

git reset --hard HEAD~1

Example:

git reset --hard origin/main

Target specific files

Unstage one file

git reset HEAD src/app.js

Example:

git reset HEAD .

Reset one file to latest commit

git checkout -- src/app.js

Example:

git restore src/app.js

Safer recovery workflow

Preview commit before reset

git show HEAD~2

Example:

git log --oneline -5

Recover with reflog if needed

git reflog

Example:

git reset --hard HEAD@{1}

Common mistakes / Pitfalls

  • Running --hard on the wrong branch deletes uncommitted work.
  • Using reset after push rewrites shared history and breaks teammates.
  • For one file, prefer git restore or checkout instead of full branch reset.

Related Cheat Sheets

Last updated: February 2026