How do you delete untracked local files from your current working tree?
30 Answers
git-clean - Remove untracked files from the working tree
Synopsis
git clean [-d] [-f] [-i] [-n] [-q] [-e <pattern>] [-x | -X] [--] <path>…
Description
Cleans the working tree by recursively removing files that are not under version control, starting from the current directory.
Normally, only files unknown to Git are removed, but if the
-x
option is specified, ignored files are also removed. This can, for example, be useful to remove all build products.If any optional
<path>...
arguments are given, only those paths are affected.
Step 1 is to show what will be deleted by using the -n
option:
# Print out the list of files and directories which will be removed (dry run)
git clean -n -d
Clean Step - beware: this will delete files:
# Delete the files from the repository
git clean -f
- To remove directories, run
git clean -f -d
orgit clean -fd
- To remove ignored files, run
git clean -f -X
orgit clean -fX
- To remove ignored and non-ignored files, run
git clean -f -x
orgit clean -fx
Note the case difference on the X
for the two latter commands.
If clean.requireForce
is set to "true" (the default) in your configuration, one needs to specify -f
otherwise nothing will actually happen.
Again see the git-clean
docs for more information.
Options
-f
,--force
If the Git configuration variable clean.requireForce is not set to false, git clean will refuse to run unless given
-f
,-n
or-i
.
-x
Don’t use the standard ignore rules read from .gitignore (per directory) and
$GIT_DIR/info/exclude
, but do still use the ignore rules given with-e
options. This allows removing all untracked files, including build products. This can be used (possibly in conjunction with git reset) to create a pristine working directory to test a clean build.
-X
Remove only files ignored by Git. This may be useful to rebuild everything from scratch, but keep manually created files.
-n
,--dry-run
Don’t actually remove anything, just show what would be done.
-d
Remove untracked directories in addition to untracked files. If an untracked directory is managed by a different Git repository, it is not removed by default. Use
-f
option twice if you really want to remove such a directory.
Use git clean -f -d
to make sure that directories are also removed.
Don’t actually remove anything, just show what would be done.
git clean -n
or
git clean --dry-run
Remove untracked directories in addition to untracked files. If an untracked directory is managed by a different Git repository, it is not removed by default. Use the
-f
option twice if you really want to remove such a directory.git clean -fd
You can then check if your files are really gone with git status
.
I am surprised nobody mentioned this before:
git clean -i
That stands for interactive and you will get a quick overview of what is going to be deleted offering you the possibility to include/exclude the affected files. Overall, still faster than running the mandatory --dry-run
before the real cleaning.
You will have to toss in a -d
if you also want to take care of empty folders. At the end, it makes for a nice alias:
git iclean
That being said, the extra hand holding of interactive commands can be tiring for experienced users. These days I just use the already mentioned git clean -fd
I like git stash push -u
because you can undo them all with git stash pop
.
EDIT: Also I found a way to show untracked file in a stash (e.g. git show stash@{0}^3
) https://stackoverflow.com/a/12681856/338986
EDIT2: git stash save
is deprecated in favor of push
. Thanks @script-wolf.
Remove all extra folders and files in this repo + submodules
This gets you in same state as fresh clone.
git clean -ffdx
Remove all extra folders and files in this repo but not its submodules
git clean -fdx
Remove extra folders but not files (ex. build or logs folder)
git clean -fd
Remove extra folders + ignored files (but not newly added files)
If file wasn't ignored and not yet checked-in then it stays. Note the capital X.
git clean -fdX
New interactive mode
git clean
OK, deleting unwanted untracked files and folders are easy using git
in command line, just do it like this:
git clean -fd
Double check before doing it as it will delete the files and folders without making any history...
Also in this case, -f
stands for force and -d
stands for directory...
So, if you want to delete files only, you can use -f
only:
git clean -f
If you want to delete(directories) and files, you can delete only untracked directories and files like this:
git clean -fd
Also, you can use -x
flag for including the files which are ignored by git. This would be helpful if you want to delete everything.
And adding -i
flag, makes git asking you for permission for deleting files one by one on the go.
If you not sure and want to check things first, add -n
flag.
Use -q
if you don't want to see any report after successful deletion.
I also create the image below to make it more memorable, especially I have seen many people confuse -f
for cleaning folder sometimes or mix it up somehow!
User interactive approach:
git clean -i -fd
Remove .classpath [y/N]? N
Remove .gitignore [y/N]? N
Remove .project [y/N]? N
Remove .settings/ [y/N]? N
Remove src/com/arsdumpgenerator/inspector/ [y/N]? y
Remove src/com/arsdumpgenerator/manifest/ [y/N]? y
Remove src/com/arsdumpgenerator/s3/ [y/N]? y
Remove tst/com/arsdumpgenerator/manifest/ [y/N]? y
Remove tst/com/arsdumpgenerator/s3/ [y/N]? y
-i for interactive
-f for force
-d for directory
-x for ignored files(add if required)
Note: Add -n or --dry-run to just check what it will do.
git clean -f -d -x $(git rev-parse --show-cdup)
applies clean to the root directory, no matter where you call it within a repository directory tree. I use it all the time as it does not force you to leave the folder where you working now and allows to clean & commit right from the place where you are.
Be sure that flags -f
, -d
, -x
match your needs:
-d
Remove untracked directories in addition to untracked files. If an
untracked directory is managed by a different Git repository, it is
not removed by default. Use -f option twice if you really want to
remove such a directory.
-f, --force
If the Git configuration variable clean.requireForce is not set to
false, git clean will refuse to delete files or directories unless
given -f, -n or -i. Git will refuse to delete directories with .git
sub directory or file unless a second -f is given. This affects
also git submodules where the storage area of the removed submodule
under .git/modules/ is not removed until -f is given twice.
-x
Don't use the standard ignore rules read from .gitignore (per
directory) and $GIT_DIR/info/exclude, but do still use the ignore
rules given with -e options. This allows removing all untracked
files, including build products. This can be used (possibly in
conjunction with git reset) to create a pristine working directory
to test a clean build.
There are other flags as well available, just check git clean --help
.
Be careful while running `git clean` command.
Always use -n
before running the actual command as it will show you what files would get removed.
git clean -n -d
git clean -f -d
By default, git clean
will only remove untracked files that are not ignored. Any file that matches a pattern in your .gitignore or other ignore files will not be removed. If you want to remove those files too, you can add a -x
to the clean command.
git clean -f -d -x
There is also interactive mode available -i
with the clean command
git clean -x -i
Alternatively
If you are not 100% sure that deleting your uncommitted work is safe, you could use stashing instead
git stash --all
It will also clear your directory but give you flexibility to retrieve the files at any point in time using stash with apply or pop. Then at later point you could clear your stash using:
git stash drop // or clean
uggested Command for Removing Untracked Files from git docs is git clean
git clean - Remove untracked files from the working tree
Suggested Method: Interative Mode by using git clean -i
so we can have control over it. let see remaining available options.
Available Options:
git clean
-d -f -i -n -q -e -x -X (can use either)
Explanation:
1. -d
Remove untracked directories in addition to untracked files. If an untracked directory is managed by a different Git repository, it is not removed by default. Use -f option twice if you really want to remove such a directory.
2. -f, --force
If the Git configuration variable clean.requireForce is not set to false, git clean will refuse to run unless given -f, -n or -i.
3. -i, --interactive
Show what would be done and clean files interactively. See “Interactive mode” for details.
4. -n, --dry-run
Don’t actually remove anything, just show what would be done.
5. -q, --quiet
Be quiet, only report errors, but not the files that are successfully removed.
6. -e , --exclude=
In addition to those found in .gitignore (per directory) and $GIT_DIR/info/exclude, also consider these patterns to be in the set of the ignore rules in effect.
7. -x
Don’t use the standard ignore rules read from .gitignore (per directory) and $GIT_DIR/info/exclude, but do still use the ignore rules given with -e options. This allows removing all untracked files, including build products. This can be used (possibly in conjunction with git reset) to create a pristine working directory to test a clean build.
8. -X
Remove only files ignored by Git. This may be useful to rebuild everything from scratch, but keep manually created files.
git clean -f to remove untracked files from working directory.
I have covered some basics here in my blog, git-intro-basic-commands
oh-my-zsh with zsh provides those great aliases via the git plugin. They can be used in bash as well.
gclean='git clean -fd'
gpristine='git reset --hard && git clean -dfx'
gclean
removes untracked directories in addition to untracked files.gpristine
hard reset the local changes, remove untracked directories, untracked files and don't use the standard ignore rules read from .gitignore (per directory) and $GIT_DIR/info/exclude, but do still use the ignore rules given with -e options. This allows removing all untracked files, including build products. This can be used (possibly in conjunction with git reset) to create a pristine working directory to test a clean build.
git clean
has now an interactive mode! See my answer to this other question: git 1.8.4+ – VonCgit clean
or some variation in the answers below, including the interactive version to delete just selective files, but interactive mode can be tedious. Whatever you do, make sure you understand whatgit clean
will delete or use--dry-run
to have it tell you without deleting anything. – LightCCrm files-to-be-deleted
– mhatch