When should I use Git revert instead of moving a branch backward?

They change different things. git revert <commit> adds a new commit that reverses changes from the selected commit; the original commit remains in history. [S1]

Reset moves the current branch’s HEAD to a different commit. Its effect on the index and working files depends on the reset mode. With --hard, tracked files are made to match the target, and untracked files may be overwritten. [S2]

In short: revert records an undo after the existing history; reset moves the branch tip. Decide based on the history you want and what should happen to your local files.

Consider git revert if you want to undo the change while leaving the existing commits in the branch’s history. It adds an undo commit rather than moving the branch tip. [S1]

Reset changes the tip. If you publish that changed branch, people who based work on its previous tip may need to reconcile the different history. That is a coordination concern, not a policy enforced by Git. The reset documentation describes command behavior, not a universal rule for shared branches. [S2]

Before changing a shared branch, check who relies on it and coordinate with them. If you are unsure, ask the repository maintainer before moving its tip.

Git requires a clean working tree for git revert, so check and preserve unfinished work before running it. A revert records changes that reverse the selected commit; merge commits have special considerations, so do not assume they work like ordinary commits. [S1]

Reset’s effects depend on the mode: it can change the index and working tree, and --hard makes tracked files match the target while possibly overwriting untracked files. [S2] Preserve work you need before resetting, especially before using --hard.

For an ordinary commit on your current branch, the command shape is git revert abc123. Here, abc123 is only a placeholder: verify the commit and branch before using the command. The example does not guarantee that the changes will apply cleanly in your repository.

Reset may fit when you intentionally want your current branch tip at an earlier commit, such as on a local branch you control. Before choosing a reset mode, check whether you need to preserve staged changes, working files, or untracked files. Reset’s effects vary by mode, and --hard can overwrite files. [S2]

Use this checklist:

1. Confirm the branch and the exact commit you intend to undo.
2. Check whether others have pulled or based work on the branch.
3. Preserve unfinished and untracked work that you need.
4. Choose revert if you want a new undo commit while retaining the earlier commit in history. [S1]
5. Choose reset only if you intend to move the branch tip, and select a mode based on the desired file and index state. [S2]
6. Pause for project guidance if the target is a merge commit or you are unsure; merge reverts have special considerations. [S1]

Neither choice guarantees the project will behave as intended afterward. Inspect the result and run the checks appropriate to your project.