Reverting Commits

Reverting creates a new commit that undoes the changes introduced by a previous commit. The original commit remains in history, making revert safe for shared branches.

To revert a single commit:
Example:
Git opens an editor to confirm the revert commit message.

To undo the most recent commit:
This is the safest way to undo a bad commit on main or develop.

To revert a range of commits:
Example:
Each commit is reverted individually.

To review changes before committing:
This applies the inverse changes but leaves them staged.

Conflicts may occur if later commits depend on reverted changes.

Steps:
1. Resolve conflicts manually
2. Stage resolved files
3. Continue revert:

Stashing is safer and reversible (covered later).

• Use revert on shared branches
• Use reset only for local history cleanup
• Revert preserves collaboration safety

• git revert undoes changes by creating a new commit.
• Reverting does not rewrite history.
• Safe for public and shared branches.
• Can revert single or multiple commits.
• Prefer revert over reset on pushed commits.