How to Safely Discard Changes in a Specific Directory with Git

Introduction

Developers often need to undo modifications in the working directory; the non‑existent git discard command is sometimes mistakenly referenced. This article shows the correct, safe ways to discard changes in a specific directory using Git's built‑in tools.

The Modern Approach: git restore

Since Git 2.23, git restore provides a clear, dedicated method for undoing changes. To revert all tracked files in a directory to the last committed state, run: git restore <path-to-directory> Example for the tests/ folder: git restore tests/ This command only affects tracked files and will not delete newly added, uncommitted files.

The Classic Command: git checkout

Before git restore existed, developers used git checkout with a double‑dash separator to discard changes: git checkout -- <path-to-directory> For the tests/ directory: git checkout -- tests/ Like git restore, this only works on tracked files.

Removing New (Untracked) Files: git clean

Untracked files are not affected by the previous commands. To delete them, use git clean with the force ( -f) and directory ( -d) flags: git clean -fd <path-to-directory> Example for tests/: git clean -fd tests/ Run a dry‑run first to preview deletions by adding the -n flag:

git clean -fdn tests/

Choosing the Right Command

Use git restore for discarding changes to tracked files, git checkout -- for legacy compatibility, and git clean when you need to remove untracked files or directories. The decision depends on the type of changes you want to discard.

Conclusion

Although git discard does not exist, Git offers effective tools for the same purpose. Modern Git users should prefer git restore for tracked files and git clean for untracked files, enabling confident and precise management of the working directory.