🚀 Git Revert: Undo Commits Without Losing History

git revert is used to undo a commit without deleting history. Unlike git reset --hard, it creates a new commit to reverse the changes.

📌 When to Use git revert?

✅ Safe for shared repositories (e.g., GitHub, GitLab, Bitbucket)
✅ Does NOT delete commits but creates a new one to undo changes
✅ Good for undoing specific commits without affecting others

1️⃣ Revert the Last Commit

git revert HEAD

➡ This reverses the last commit and creates a new commit.

2️⃣ Revert a Specific Commit

1️⃣ Find the commit hash:

git log --oneline

Example output:

a1b2c3d Fixed a bugf6g7h8i Added new feature

2️⃣ Revert that commit:

git revert a1b2c3d

➡ This creates a new commit that undoes only that commit, keeping others intact.

3️⃣ Revert Multiple Commits

git revert HEAD~2..HEAD

➡ This reverts the last two commits (HEAD to HEAD~2).

4️⃣ Revert Without Creating a Commit

If you don’t want an automatic commit, use:

git revert -n <commit-hash>

➡ Changes will be staged, and you can commit manually:

git commit -m "Reverted commit <hash>"

🔥 Example Workflow

git log --onelinegit revert f6g7h8i  # Reverts "Added new feature"git push origin main

🎯 Summary

💡 Use git revert instead of git reset --hard for safe changes in shared repositories.