Thank for this,
I think it's also worth mentioning about git revert 1fc6665 which contrary to git reset --hard 1fc6665 will not remove completely the commit from the history but will create a new commit that reverses the specified commit and won't delete it from the history as git reset does, so that if later you realize that those changes were not so bad you can come back to them easily again 😄
NB: With git reset, you'll be oblige to git push -f (Forcing updating of the upstream)
git revert 1fc6665
git reset --hard 1fc6665
git push -f
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.