How can I restore one file from an earlier Git commit?

Use git restore with the earlier commit and the file path:

git restore --source <commit> -- <path>

Replace <commit> with the commit you want to take the file from and <path> with its path in the repository. For example, if the placeholders were abc123 and notes.md, the command would be git restore --source abc123 -- notes.md.

This restores that path’s contents in your working tree; it does not move the branch. That is different from trying to move the repository’s branch back to an earlier point. Pause before running it, though: restoring a path can replace its current contents, and if the path is absent from the chosen commit, it may be removed. [S1]

Start with git status. It reports changes between the current commit (HEAD) and the index, changes between the index and working tree, and untracked paths. git status -v can show staged textual changes; repeating the option also shows unstaged textual changes. [S2]

Read the status output and decide whether the current version contains anything you need. Status helps you identify work to preserve, but it does not back that work up. If you are unsure, stop before restoring and make a separate copy of the file outside the repository, using a clearly labeled name such as [backup-name]. Then you have a reference if the current edits matter.

Assume you want draft.md from commit abc123; those names are examples, not values to copy blindly.

1. Run git status -v and review the output for draft.md. Look for staged and unstaged edits, as well as untracked work you may need to keep. [S2]
2. If the present file has edits you want, preserve them first. A separate copy outside the repository is a simple manual option. Do not treat the status output itself as a backup.
3. Once you have identified the right commit and path, run git restore --source abc123 -- draft.md. This targets the working-tree file and does not move the branch. [S1]
4. Inspect the restored file and run git status again. Confirm the working-tree contents are what you intended before taking any further action.

Be especially deliberate if the file is staged: Git distinguishes the index from the working tree, and the default restore location is the working tree. The --staged option affects the index instead. Do not add --staged unless you specifically intend to restore the index as well. [S1][S2]

Afterward, open the file and compare its contents with what you meant to retrieve; then run git status to review the repository state. If the result is surprising, stop and consult the separate copy you made rather than assuming the prior edits are still present. Status can show repository changes, but it does not establish that the chosen commit was the one you intended. [S2]

A path absent from the selected commit may be removed by the restore operation. [S1] If you are uncertain whether it exists there, verify your intended commit and path before running the command. These steps restore content in the working tree; they do not determine whether or when you should commit the result.