One command could fix it—or destroy hours of work. That’s when you realize Git reset is not forgiving. Precision matters. Every flag, every scope, every choice can mean the difference between a clean history and irreversible loss.
Git reset has three primary modes: --soft, --mixed, and --hard. Each changes different parts of your repository state. --soft moves HEAD but leaves both the index and working directory intact. It’s for regrouping commits without touching actual file changes. --mixed—the default—moves HEAD and resets the index, but preserves working files. Use it to re-stage from scratch. --hard resets everything: HEAD, index, and working directory. It leaves nothing behind.
Precision starts before you type the command. Always confirm the commit hash with git log --oneline or git reflog. Target exactly what you want to reset to. Avoid typing HEAD~ in anger. Reflog will save you sometimes, but not always. Keep destructive commands local until you’re certain. Once you’ve pushed a reset, the rest of the team sees history rewritten. That can mean merge conflicts, broken builds, and wasted debugging cycles. If you must rewrite public history, coordinate and document the exact steps.