3 .\" Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author]
4 .\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
7 .\" Source: Git 2.42.0.176.gd6c51973e4
10 .TH "GIT\-CLEAN" "1" "2023\-09\-13" "Git 2\&.42\&.0\&.176\&.gd6c519" "Git Manual"
11 .\" -----------------------------------------------------------------
12 .\" * Define some portability stuff
13 .\" -----------------------------------------------------------------
14 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
15 .\" http://bugs.debian.org/507673
16 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
17 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
20 .\" -----------------------------------------------------------------
21 .\" * set default formatting
22 .\" -----------------------------------------------------------------
23 .\" disable hyphenation
25 .\" disable justification (adjust text to left margin only)
27 .\" -----------------------------------------------------------------
28 .\" * MAIN CONTENT STARTS HERE *
29 .\" -----------------------------------------------------------------
31 git-clean \- Remove untracked files from the working tree
35 \fIgit clean\fR [\-d] [\-f] [\-i] [\-n] [\-q] [\-e <pattern>] [\-x | \-X] [\-\-] [<pathspec>\&...]
40 Cleans the working tree by recursively removing files that are not under version control, starting from the current directory\&.
42 Normally, only files unknown to Git are removed, but if the \fB\-x\fR option is specified, ignored files are also removed\&. This can, for example, be useful to remove all build products\&.
44 If any optional \fB<pathspec>\&.\&.\&.\fR arguments are given, only those paths that match the pathspec are affected\&.
49 Normally, when no <pathspec> 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 a <pathspec> is specified, \-d is irrelevant; all untracked files matching the specified paths (with exceptions for nested git directories mentioned under
50 \fB\-\-force\fR) will be removed\&.
55 If the Git configuration variable clean\&.requireForce is not set to false,
57 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\&.
62 Show what would be done and clean files interactively\&. See \(lqInteractive mode\(rq for details\&.
67 Don\(cqt actually remove anything, just show what would be done\&.
72 Be quiet, only report errors, but not the files that are successfully removed\&.
75 \-e <pattern>, \-\-exclude=<pattern>
77 Use the given exclude pattern in addition to the standard ignore rules (see
78 \fBgitignore\fR(5))\&.
83 Don\(cqt use the standard ignore rules (see
84 \fBgitignore\fR(5)), but still use the ignore rules given with
86 options from the command line\&. This allows removing all untracked files, including build products\&. This can be used (possibly in conjunction with
89 \fIgit reset\fR) to create a pristine working directory to test a clean build\&.
94 Remove only files ignored by Git\&. This may be useful to rebuild everything from scratch, but keep manually created files\&.
96 .SH "INTERACTIVE MODE"
98 When the command enters the interactive mode, it shows the files and directories to be cleaned, and goes into its interactive command loop\&.
100 The command loop shows the list of subcommands available, and gives a prompt "What now> "\&. In general, when the prompt ends with a single \fI>\fR, you can pick only one of the choices given and type return, like this:
107 1: clean 2: filter by pattern 3: select by numbers
108 4: ask each 5: quit 6: help
116 You also could say \fBc\fR or \fBclean\fR above as long as the choice is unique\&.
118 The main command loop has 6 subcommands\&.
122 Start cleaning files and directories, and then quit\&.
127 This shows the files and directories to be deleted and issues an "Input ignore patterns>>" prompt\&. You can input space\-separated patterns to exclude files and directories from deletion\&. E\&.g\&. "*\&.c *\&.h" will excludes files end with "\&.c" and "\&.h" from deletion\&. When you are satisfied with the filtered result, press ENTER (empty) back to the main menu\&.
132 This shows the files and directories to be deleted and issues an "Select items to delete>>" prompt\&. When the prompt ends with double
134 like this, you can make more than one selection, concatenated with whitespace or comma\&. Also you can say ranges\&. E\&.g\&. "2\-5 7,9" to choose 2,3,4,5,7,9 from the list\&. If the second number in a range is omitted, all remaining items are selected\&. E\&.g\&. "7\-" to choose 7,8,9 from the list\&. You can say
136 to choose everything\&. Also when you are satisfied with the filtered result, press ENTER (empty) back to the main menu\&.
141 This will start to clean, and you must confirm one by one in order to delete items\&. Please note that this action is not as efficient as the above two actions\&.
146 This lets you quit without do cleaning\&.
151 Show brief usage of interactive git\-clean\&.
155 Everything below this line in this section is selectively included from the \fBgit-config\fR(1) documentation\&. The content is the same as what\(cqs found there:
159 A boolean to make git\-clean do nothing unless given \-f, \-i or \-n\&. Defaults to true\&.
166 Part of the \fBgit\fR(1) suite