How can I unstage a file without discarding its edits?

Unstaging removes a file from the changes selected for the next commit. It is different from discarding the edits in your working copy. In Visual Studio, staged and modified, unstaged changes appear in separate sections, and only the staged section is included in a staged commit. [S1]

So your goal is to change the file’s staging status, not its contents. Use an unstage action; avoid actions labeled discard or revert when you want to keep the edits.

In the Git Changes view, find the file under Staged Changes and click its minus button. Microsoft documents this button as the way to unstage a file. [S1]

Before acting, confirm the file’s name so you unstage the intended item. Afterward, check both sections in Git Changes: the file should no longer be under Staged Changes and should appear among modified, unstaged Changes if its edits remain. This before-and-after check helps confirm that it is no longer selected for the staged commit while its working-copy changes are still present. [S1]

If the result is unexpected, pause and inspect the Git Changes view rather than choosing a discard action.

For a single file, run git reset <file_path>, replacing the placeholder with the path to your file. For example, for notes.txt, run git reset notes.txt. Microsoft documents this as the command-line equivalent of unstaging a single file in the Visual Studio workflow. The guidance also says a directory path can be used to unstage a directory. [S1]

Treat <file_path> as a placeholder, not text to type literally. After running the command, check the resulting Git Changes view: the file should be outside the staged section and appear as an unstaged modification if its edits remain. This guidance covers the Visual Studio workflow and its documented equivalent command; it does not establish behavior for every client or unusual repository state. [S1]

Use this sequence:

1. Identify the exact file you want to unstage.
2. Check that it is listed under Staged Changes, or note its exact path for the command line.
3. Unstage only that file: click its minus button in Visual Studio, or run git reset <file_path>. [S1]
4. Check Git Changes again. Look for the file outside Staged Changes and among modified, unstaged Changes if its edits remain. [S1]
5. If the result is unexpected, stop and inspect the file and its status. Don’t substitute a discard action.

For example, if report.md is staged, run git reset report.md, then check that it appears as an unstaged modification. The goal is to change the staging selection, not to discard the edits. [S1]