Git Reset vs. Revert: Differences and Use Cases

In Git, "Reset" and "Undo" have different principles and impacts: Reset directly rewrites history, suitable for local, unpushed "draft" scenarios; Undo preserves history through new commits or recovery operations, suitable for error correction requiring trace retention (e.g., remote branches). Reset has three modes: `--soft` only moves HEAD without changing the staging area/workspace, ideal for amending commit messages; `--mixed` moves HEAD and resets the staging area, suitable for undoing mistakenly `add`ed files; `--hard` completely resets the workspace, ideal for discarding local incorrect modifications. Undo core principles focus on not rewriting history: `git revert` creates reverse commits to preserve remote history; `git checkout` restores files or branches; `git commit --amend` modifies the most recent commit; `git stash` stashes uncommitted changes. Key differences: Reset modifies history (local unpushed), Undo retains traces (remote or historical requirements). Pitfalls: Use Revert for remote errors, Reset for local unpushed, and cautiously use `--force`.