Resetting Commits

Resetting moves HEAD to an earlier commit. Depending on the reset type, Git may also modify the staging area and working directory. This is used only on local commits.

Moves HEAD backward but keeps changes staged.
Use case:
• Edit or combine recent commits
• Change commit message or grouping

Example:

Moves HEAD backward and unstages changes but keeps file modifications.
or explicitly:
Use case:
• Rework staged files
• Reorganize commits

Moves HEAD backward and discards all changes.
Use case:
• Throw away commits and changes completely
⚠️ Irreversible if commits are not backed up.

Reset directly using commit hash:
Git history beyond that commit is removed from the current branch.

• Reset rewrites history (local only)
• Revert creates a new commit (safe for shared branches)
Never reset commits that have already been pushed to shared branches.

• Use reset only on local branches
• Avoid --hard unless certain
• Prefer revert for public history
• Backup commit hashes if unsure

• git reset moves HEAD backward.
• --soft keeps changes staged.
• --mixed keeps changes unstaged (default).
• --hard deletes commits and changes permanently.
• Never reset shared or pushed commits.