A bad commit that broke Ansible inventory parsing is already on the…

Question

A bad commit that broke Ansible inventory parsing is already on the shared main branch and teammates have fetched it. How should the team undo that change safely?

Accepted Answer

git revert to add a new commit that applies the inverse while leaving history intact. — Once the bad change is in everyone’s hands, you do not rip pages from the shared book—you add a new page that crosses out the mistake. That new page is git revert. Resetting shared main and force-pushing breaks teammates who already fetched.

Answer

git reset --hard on shared main and force-push so everyone’s history is rewritten.

Answer

Delete the remote repository and recreate it without the commit.

Answer

git checkout of an unrelated tag and abandon main permanently.

A bad commit that broke Ansible inventory parsing is already on the shared main branch and teammates have fetched it. How should the team undo that change safely?

Short Explanation

Full Explanation