Add an optional <mode> argument to commit/status -u|--untracked-files option
[git/git.git] / Documentation / git-commit.txt
1 git-commit(1)
2 =============
5 ----
6 git-commit - Record changes to the repository
9 --------
10 [verse]
11 'git-commit' [-a | --interactive] [-s] [-v] [-u[<mode>]]
12 [(-c | -C) <commit> | -F <file> | -m <msg> | --amend]
13 [--allow-empty] [--no-verify] [-e] [--author <author>]
14 [--cleanup=<mode>] [--] [[-i | -o ]<file>...]
17 -----------
18 Use 'git commit' to store the current contents of the index in a new
19 commit along with a log message describing the changes you have made.
21 The content to be added can be specified in several ways:
23 1. by using linkgit:git-add[1] to incrementally "add" changes to the
24 index before using the 'commit' command (Note: even modified
25 files must be "added");
27 2. by using linkgit:git-rm[1] to remove files from the working tree
28 and the index, again before using the 'commit' command;
30 3. by listing files as arguments to the 'commit' command, in which
31 case the commit will ignore changes staged in the index, and instead
32 record the current content of the listed files;
34 4. by using the -a switch with the 'commit' command to automatically
35 "add" changes from all known files (i.e. all files that are already
36 listed in the index) and to automatically "rm" files in the index
37 that have been removed from the working tree, and then perform the
38 actual commit;
40 5. by using the --interactive switch with the 'commit' command to decide one
41 by one which files should be part of the commit, before finalizing the
42 operation. Currently, this is done by invoking `git-add --interactive`.
44 The linkgit:git-status[1] command can be used to obtain a
45 summary of what is included by any of the above for the next
46 commit by giving the same set of parameters you would give to
47 this command.
49 If you make a commit and then found a mistake immediately after
50 that, you can recover from it with linkgit:git-reset[1].
54 -------
55 -a|--all::
56 Tell the command to automatically stage files that have
57 been modified and deleted, but new files you have not
58 told git about are not affected.
60 -c or -C <commit>::
61 Take existing commit object, and reuse the log message
62 and the authorship information (including the timestamp)
63 when creating the commit. With '-C', the editor is not
64 invoked; with '-c' the user can further edit the commit
65 message.
67 -F <file>::
68 Take the commit message from the given file. Use '-' to
69 read the message from the standard input.
71 --author <author>::
72 Override the author name used in the commit. Use
73 `A U Thor <>` format.
75 -m <msg>|--message=<msg>::
76 Use the given <msg> as the commit message.
78 -t <file>|--template=<file>::
79 Use the contents of the given file as the initial version
80 of the commit message. The editor is invoked and you can
81 make subsequent changes. If a message is specified using
82 the `-m` or `-F` options, this option has no effect. This
83 overrides the `commit.template` configuration variable.
85 -s|--signoff::
86 Add Signed-off-by line at the end of the commit message.
88 --no-verify::
89 This option bypasses the pre-commit and commit-msg hooks.
90 See also linkgit:githooks[5][hooks].
92 --allow-empty::
93 Usually recording a commit that has the exact same tree as its
94 sole parent commit is a mistake, and the command prevents you
95 from making such a commit. This option bypasses the safety, and
96 is primarily for use by foreign scm interface scripts.
98 --cleanup=<mode>::
99 This option sets how the commit message is cleaned up.
100 The '<mode>' can be one of 'verbatim', 'whitespace', 'strip',
101 and 'default'. The 'default' mode will strip leading and
102 trailing empty lines and #commentary from the commit message
103 only if the message is to be edited. Otherwise only whitespace
104 removed. The 'verbatim' mode does not change message at all,
105 'whitespace' removes just leading/trailing whitespace lines
106 and 'strip' removes both whitespace and commentary.
108 -e|--edit::
109 The message taken from file with `-F`, command line with
110 `-m`, and from file with `-C` are usually used as the
111 commit log message unmodified. This option lets you
112 further edit the message taken from these sources.
114 --amend::
116 Used to amend the tip of the current branch. Prepare the tree
117 object you would want to replace the latest commit as usual
118 (this includes the usual -i/-o and explicit paths), and the
119 commit log editor is seeded with the commit message from the
120 tip of the current branch. The commit you create replaces the
121 current tip -- if it was a merge, it will have the parents of
122 the current tip as parents -- so the current top commit is
123 discarded.
124 +
125 --
126 It is a rough equivalent for:
127 ------
128 $ git reset --soft HEAD^
129 $ ... do something else to come up with the right tree ...
130 $ git commit -c ORIG_HEAD
132 ------
133 but can be used to amend a merge commit.
134 --
136 -i|--include::
137 Before making a commit out of staged contents so far,
138 stage the contents of paths given on the command line
139 as well. This is usually not what you want unless you
140 are concluding a conflicted merge.
142 -o|--only::
143 Make a commit only from the paths specified on the
144 command line, disregarding any contents that have been
145 staged so far. This is the default mode of operation of
146 'git commit' if any paths are given on the command line,
147 in which case this option can be omitted.
148 If this option is specified together with '--amend', then
149 no paths need be specified, which can be used to amend
150 the last commit without committing changes that have
151 already been staged.
153 -u[<mode>]|--untracked-files[=<mode>]::
154 Show untracked files (Default: 'all').
155 +
156 The mode parameter is optional, and is used to specify
157 the handling of untracked files. The possible options are:
158 +
159 --
160 - 'normal' - Shows untracked files and directories
161 - 'all' - Also shows individual files in untracked directories.
162 --
164 -v|--verbose::
165 Show unified diff between the HEAD commit and what
166 would be committed at the bottom of the commit message
167 template. Note that this diff output doesn't have its
168 lines prefixed with '#'.
170 -q|--quiet::
171 Suppress commit summary message.
173 \--::
174 Do not interpret any more arguments as options.
176 <file>...::
177 When files are given on the command line, the command
178 commits the contents of the named files, without
179 recording the changes already staged. The contents of
180 these files are also staged for the next commit on top
181 of what have been staged before.
185 --------
186 When recording your own work, the contents of modified files in
187 your working tree are temporarily stored to a staging area
188 called the "index" with linkgit:git-add[1]. A file can be
189 reverted back, only in the index but not in the working tree,
190 to that of the last commit with `git-reset HEAD -- <file>`,
191 which effectively reverts `git-add` and prevents the changes to
192 this file from participating in the next commit. After building
193 the state to be committed incrementally with these commands,
194 `git commit` (without any pathname parameter) is used to record what
195 has been staged so far. This is the most basic form of the
196 command. An example:
198 ------------
199 $ edit hello.c
200 $ git rm goodbye.c
201 $ git add hello.c
202 $ git commit
203 ------------
205 Instead of staging files after each individual change, you can
206 tell `git commit` to notice the changes to the files whose
207 contents are tracked in
208 your working tree and do corresponding `git add` and `git rm`
209 for you. That is, this example does the same as the earlier
210 example if there is no other change in your working tree:
212 ------------
213 $ edit hello.c
214 $ rm goodbye.c
215 $ git commit -a
216 ------------
218 The command `git commit -a` first looks at your working tree,
219 notices that you have modified hello.c and removed goodbye.c,
220 and performs necessary `git add` and `git rm` for you.
222 After staging changes to many files, you can alter the order the
223 changes are recorded in, by giving pathnames to `git commit`.
224 When pathnames are given, the command makes a commit that
225 only records the changes made to the named paths:
227 ------------
228 $ edit hello.c hello.h
229 $ git add hello.c hello.h
230 $ edit Makefile
231 $ git commit Makefile
232 ------------
234 This makes a commit that records the modification to `Makefile`.
235 The changes staged for `hello.c` and `hello.h` are not included
236 in the resulting commit. However, their changes are not lost --
237 they are still staged and merely held back. After the above
238 sequence, if you do:
240 ------------
241 $ git commit
242 ------------
244 this second commit would record the changes to `hello.c` and
245 `hello.h` as expected.
247 After a merge (initiated by either linkgit:git-merge[1] or
248 linkgit:git-pull[1]) stops because of conflicts, cleanly merged
249 paths are already staged to be committed for you, and paths that
250 conflicted are left in unmerged state. You would have to first
251 check which paths are conflicting with linkgit:git-status[1]
252 and after fixing them manually in your working tree, you would
253 stage the result as usual with linkgit:git-add[1]:
255 ------------
256 $ git status | grep unmerged
257 unmerged: hello.c
258 $ edit hello.c
259 $ git add hello.c
260 ------------
262 After resolving conflicts and staging the result, `git ls-files -u`
263 would stop mentioning the conflicted path. When you are done,
264 run `git commit` to finally record the merge:
266 ------------
267 $ git commit
268 ------------
270 As with the case to record your own changes, you can use `-a`
271 option to save typing. One difference is that during a merge
272 resolution, you cannot use `git commit` with pathnames to
273 alter the order the changes are committed, because the merge
274 should be recorded as a single commit. In fact, the command
275 refuses to run when given pathnames (but see `-i` option).
279 ----------
281 Though not required, it's a good idea to begin the commit message
282 with a single short (less than 50 character) line summarizing the
283 change, followed by a blank line and then a more thorough description.
284 Tools that turn commits into email, for example, use the first line
285 on the Subject: line and the rest of the commit in the body.
287 include::i18n.txt[]
290 ---------------------------------------
291 The editor used to edit the commit log message will be chosen from the
292 GIT_EDITOR environment variable, the core.editor configuration variable, the
293 VISUAL environment variable, or the EDITOR environment variable (in that
294 order).
297 -----
298 This command can run `commit-msg`, `prepare-commit-msg`, `pre-commit`,
299 and `post-commit` hooks. See linkgit:githooks[5][hooks] for more
300 information.
304 --------
305 linkgit:git-add[1],
306 linkgit:git-rm[1],
307 linkgit:git-mv[1],
308 linkgit:git-merge[1],
309 linkgit:git-commit-tree[1]
311 Author
312 ------
313 Written by Linus Torvalds <> and
314 Junio C Hamano <>
317 GIT
318 ---
319 Part of the linkgit:git[1] suite