Gitoryxgit reset is one of Git's most powerful — and most misunderstood — commands. This guide explains the three modes (--soft, --mixed, --hard), when each is safe to use, and how to recover if you go too far.
You committed too early, staged the wrong file, or want to throw away some changes entirely — but you're scared to touch `git reset` because you've heard it can destroy work.
git reset is one of the most useful undoing tools in Git. The key is understanding which of its three modes moves what: the commit pointer (HEAD), the staging area (index), and the working directory. Once you understand that, it stops being scary.
Common mistakes developers make with this:
Gitoryx: Gitoryx lets you right-click any commit in the graph and choose Reset to here — soft, mixed, or hard — with a clear description of what each mode will do before you confirm.
`git reset` moves the current branch pointer (HEAD) to a different commit, optionally changing the staging area and working directory. The three modes are: `--soft` (moves HEAD only), `--mixed` (default — also clears the staging area), and `--hard` (also discards working directory changes).
The most common everyday use: you staged something by accident and want to unstage it without changing the file.
git reset HEAD src/config.ts
# or with modern Git:
git restore --staged src/config.tsThis doesn't change the file contents — it just removes it from the staging area.
`--soft` moves HEAD back by one commit but leaves all changes staged. Useful when you want to rewrite the commit message or split the commit.
git reset --soft HEAD~1
# Your changes are still staged — just re-commit:
git commit -m "better message this time"`--mixed` (the default) moves HEAD back and unstages the changes. The files are still modified in your working directory.
git reset HEAD~1
# equivalent to:
git reset --mixed HEAD~1This is the safest way to undo a commit — you lose nothing, you just need to re-stage and re-commit.
`--hard` moves HEAD back and discards all changes in the staging area and working directory. The files are reverted to exactly the state they were in at the target commit.
git reset --hard HEAD~1`--hard` permanently discards uncommitted changes. There is no undo — unless you have the original SHA and use `git reflog` to recover it. Use with extreme caution.
See this workflow in Gitoryx. Right-click any commit in the graph to reset to it
Free downloadInstead of `HEAD~1`, you can target any commit by its SHA.
git log --oneline
# a3f2c1d add login form
# 9b1e4fa init project
git reset --soft 9b1e4faIf you ran `--hard` by mistake, your commits are still in Git's reflog for 30 days. Find the SHA and reset back to it.
git reflog
# HEAD@{1}: reset: moving to HEAD~1
# a3f2c1d HEAD@{2}: commit: add login form ← this is what we lost
git reset --hard a3f2c1dMost of the time you want to undo a commit but keep the code. `--hard` throws the code away too.
Fix: Default to `--soft` or `--mixed`. Only use `--hard` when you're certain you want to discard the changes.
This rewrites shared history. Teammates whose branches are based on the old commit will have a diverged history and will be forced to reconcile it.
Fix: Use `git revert` for commits already pushed to a shared branch. It creates a new commit that undoes the changes, without rewriting history.
Using `HEAD~5` when you meant `HEAD~1` undoes more history than intended.
Fix: Use `git log --oneline` to count commits carefully, or use the exact SHA instead of `HEAD~N`.
Gitoryx — macOS, Windows & Linux`git reset` moves the branch pointer backwards, rewriting history. `git revert` creates a new commit that undoes a previous commit's changes, preserving history. Use `reset` for local commits; use `revert` for pushed commits.
Yes, if you act quickly. Run `git reflog` to find the SHA of the commit you lost, then `git reset --hard <sha>` to restore it. Git keeps reflog entries for 30 days by default.
It moves the current branch back by one commit (--mixed by default). The changes from that commit are kept in your working directory but are no longer staged.
Run `git reset HEAD <file>` or `git restore --staged <file>` (Git 2.23+). This removes the file from the staging area while keeping your changes intact.
Everything in this tutorial is faster and clearer with a visual Git client. Gitoryx is free, runs natively on macOS, Windows, and Linux, and built for developers who want to move fast without breaking things.