You were just about there:

I opened up Git > Manage Branches and see the commit i did and see a couple of options.

You'll want to learn more about the different git reset options and how they work, but the two reset options that Visual Studio offers are --mixed and --hard. To use the reset option, in the branch history graph, select the commit that you wish to reset your branch pointer to, and this will remove all of the commits above it (and if a merge commit is being removed it will also remove all commits brought in by that merge).

For your use case where you have one commit that you wish to remove, and re-commit some of it, select the parent commit of that commit (the one below your commit in the graph), right click on it, and select "Reset->Keep Changes (--mixed)". This will put you back into the state you were in before you created the commit, with nothing staged yet.

Side Notes:

• If you don't want to keep any of your changes, you should choose --hard.
• Note that VS doesn't offer the option to do a --soft reset in the GUI, but the only difference with --soft is that all your changes would be staged already, which you can manually do in the GUI after reset with --mixed.
• The GUI command is identical to running the following command from the command line, e.g. a mixed reset: git reset --mixed <selected-commit-id>

Open the history tab in Team Explorer from the Branches tile (right-click your branch). Then in the history right-click the commit before the one you don't want to push, choose Reset. That will move the branch back to that commit and should get rid of the extra commit you made. In order to reset before a given commit you thus have to select its parent.

Depending on what you want to do with the changes choose hard, which will get rid of them locally. Or choose soft which will undo the commit but will leave your working directory with the changes in your discarded commit.

Selected answer is not correct. In order to undo a commit you need to select reset, not revert. Revvert will make a new commit with code contained in previous commit. Where reset will actually delete the commits after the selected version.

To reset HEAD back one commit and keep the changes so you can break it up into smaller commits, choose "Reset and Keep Changes (--mixed)". This runs "git reset --mixed" on the command line, which moves the HEAD ref but leaves the workdir alone. Therefore all of your changed files will appear in the Changes page.

The other option (--hard), will reset both the HEAD ref and update the workdir to match the repository at that commit. This would discard your changes.

To clarify, you'll want to view history for your branch and choose reset on the commit just before your new commit. In other words, you are resetting HEAD to that parent commit, but leaving the workdir matching your current commit. This will result in all changes in that commit being available in the workdir for subdivision into new commits.

Hope this helps.

This will cover CLI instructions, since I'm not familiar with the Visual Studio interface. You can put the commands in your terminal. Ensure your current working directory is set to the root of your local repository.

If your goal is just to revert to exactly what's on the remote, then that should be fairly simple.

Please ensure this is 100% what you want to do before you execute the commands. It can be difficult or impossible to recover the data.

First, reset all tracked files in the repository. So, all modified/deleted files. This will reset everything except any new files you created.

git reset --hard origin/main

More Info: https://git-scm.com/docs/git-reset

If your remote name or branch name is different, use those values instead. You can use git remote and git branch to check the names of remotes and branches on the repository.

Now delete all untracked files in the repository, so new files you created but have never committed yet:

git clean -f

More Info: https://git-scm.com/docs/git-clean

This isn't part of the question… but just in case.

If you find that you accidentally deleted a local commit that you need back, immediately stop what you're doing and look into git reflog to try and recover it!

If you accidentally delete files you never committed and realized you needed, Git can't help you here. You'd have to look into software for undeleting files, results may vary.