Git clean: Difference between revisions
(→-f) |
(→-x) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 7: | Line 7: | ||
Removes untracked files from the working tree: | Removes untracked files from the working tree: | ||
<syntaxhighlight lang='bash'> | |||
git clean [-f] <file|dir> | |||
</syntaxhighlight> | |||
To restore tracked files to the state present on a branch, use [[git reset]]. | |||
=Options= | =Options= | ||
| Line 15: | Line 19: | ||
==-d== | ==-d== | ||
Normally, when no path is specified, git clean will not recurse into untracked directories to avoid removing too much. Specify -d to have it recurse into such directories as well. If any paths are specified, -d is irrelevant; all untracked files matching the specified paths (with exceptions for nested git directories mentioned under --force) will be removed. | |||
==-x== | |||
Remove present files that are ignored due to their presence in .gitingore. | |||
Latest revision as of 04:44, 3 December 2020
Internal
Overview
Removes untracked files from the working tree:
git clean [-f] <file|dir>
To restore tracked files to the state present on a branch, use git reset.
Options
-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 or -i. Git will refuse to modify untracked nested git repositories (directories with a .git subdirectory) unless a second -f is given.
-d
Normally, when no path is specified, git clean will not recurse into untracked directories to avoid removing too much. Specify -d to have it recurse into such directories as well. If any paths are specified, -d is irrelevant; all untracked files matching the specified paths (with exceptions for nested git directories mentioned under --force) will be removed.
-x
Remove present files that are ignored due to their presence in .gitingore.