]>
Commit | Line | Data |
---|---|---|
215a7ad1 JH |
1 | git-commit(1) |
2 | ============= | |
62033318 JH |
3 | |
4 | NAME | |
5 | ---- | |
c3f0baac | 6 | git-commit - Record changes to the repository |
62033318 JH |
7 | |
8 | SYNOPSIS | |
9 | -------- | |
353ce815 | 10 | [verse] |
b4bd4668 CI |
11 | 'git commit' [-a | --interactive | --patch] [-s] [-v] [-u<mode>] [--amend] |
12 | [--dry-run] [(-c | -C | --fixup | --squash) <commit>] | |
13 | [-F <file> | -m <msg>] [--reset-author] [--allow-empty] | |
14 | [--allow-empty-message] [--no-verify] [-e] [--author=<author>] | |
15 | [--date=<date>] [--cleanup=<mode>] [--status | --no-status] | |
098bbdc3 | 16 | [-i | -o] [-S[<keyid>]] [--] [<file>...] |
62033318 JH |
17 | |
18 | DESCRIPTION | |
19 | ----------- | |
d69806d1 JN |
20 | Stores the current contents of the index in a new commit along |
21 | with a log message from the user describing the changes. | |
62033318 | 22 | |
a76c2acb | 23 | The content to be added can be specified in several ways: |
f9935bf9 | 24 | |
0b444cdb | 25 | 1. by using 'git add' to incrementally "add" changes to the |
a76c2acb | 26 | index before using the 'commit' command (Note: even modified |
6c96753d | 27 | files must be "added"); |
5bfc4f23 | 28 | |
0b444cdb | 29 | 2. by using 'git rm' to remove files from the working tree |
a76c2acb | 30 | and the index, again before using the 'commit' command; |
6c96753d | 31 | |
a76c2acb BF |
32 | 3. by listing files as arguments to the 'commit' command, in which |
33 | case the commit will ignore changes staged in the index, and instead | |
6fc4a7e5 MB |
34 | record the current content of the listed files (which must already |
35 | be known to git); | |
6c96753d | 36 | |
a76c2acb BF |
37 | 4. by using the -a switch with the 'commit' command to automatically |
38 | "add" changes from all known files (i.e. all files that are already | |
39 | listed in the index) and to automatically "rm" files in the index | |
40 | that have been removed from the working tree, and then perform the | |
41 | actual commit; | |
6c96753d | 42 | |
b4bd4668 CI |
43 | 5. by using the --interactive or --patch switches with the 'commit' command |
44 | to decide one by one which files or hunks should be part of the commit, | |
6cf378f0 | 45 | before finalizing the operation. See the ``Interactive Mode'' section of |
b4bd4668 | 46 | linkgit:git-add[1] to learn how to operate these modes. |
6cbf07ef | 47 | |
60c2993c | 48 | The `--dry-run` option can be used to obtain a |
6c96753d | 49 | summary of what is included by any of the above for the next |
60c2993c | 50 | commit by giving the same set of parameters (options and paths). |
6c96753d | 51 | |
483bc4f0 | 52 | If you make a commit and then find a mistake immediately after |
0b444cdb | 53 | that, you can recover from it with 'git reset'. |
5bfc4f23 | 54 | |
6d35cc76 | 55 | |
62033318 JH |
56 | OPTIONS |
57 | ------- | |
3240240f SB |
58 | -a:: |
59 | --all:: | |
6c96753d JH |
60 | Tell the command to automatically stage files that have |
61 | been modified and deleted, but new files you have not | |
62 | told git about are not affected. | |
62033318 | 63 | |
b4bd4668 CI |
64 | -p:: |
65 | --patch:: | |
66 | Use the interactive patch selection interface to chose | |
67 | which changes to commit. See linkgit:git-add[1] for | |
68 | details. | |
69 | ||
3240240f SB |
70 | -C <commit>:: |
71 | --reuse-message=<commit>:: | |
bc47c29e | 72 | Take an existing commit object, and reuse the log message |
62033318 | 73 | and the authorship information (including the timestamp) |
bc47c29e | 74 | when creating the commit. |
62033318 | 75 | |
3240240f SB |
76 | -c <commit>:: |
77 | --reedit-message=<commit>:: | |
bc47c29e SB |
78 | Like '-C', but with '-c' the editor is invoked, so that |
79 | the user can further edit the commit message. | |
80 | ||
d71b8ba7 PN |
81 | --fixup=<commit>:: |
82 | Construct a commit message for use with `rebase --autosquash`. | |
83 | The commit message will be the subject line from the specified | |
84 | commit with a prefix of "fixup! ". See linkgit:git-rebase[1] | |
85 | for details. | |
86 | ||
89ac1223 PN |
87 | --squash=<commit>:: |
88 | Construct a commit message for use with `rebase --autosquash`. | |
89 | The commit message subject line is taken from the specified | |
90 | commit with a prefix of "squash! ". Can be used with additional | |
91 | commit message options (`-m`/`-c`/`-C`/`-F`). See | |
92 | linkgit:git-rebase[1] for details. | |
93 | ||
c51f6cee | 94 | --reset-author:: |
37f7a857 JS |
95 | When used with -C/-c/--amend options, or when committing after a |
96 | a conflicting cherry-pick, declare that the authorship of the | |
97 | resulting commit now belongs of the committer. This also renews | |
98 | the author timestamp. | |
c51f6cee | 99 | |
7c9f7038 JK |
100 | --short:: |
101 | When doing a dry-run, give the output in the short-format. See | |
102 | linkgit:git-status[1] for details. Implies `--dry-run`. | |
103 | ||
e858af6d RR |
104 | --branch:: |
105 | Show the branch and tracking info even in short-format. | |
106 | ||
7c9f7038 JK |
107 | --porcelain:: |
108 | When doing a dry-run, give the output in a porcelain-ready | |
109 | format. See linkgit:git-status[1] for details. Implies | |
110 | `--dry-run`. | |
111 | ||
f3f47a1e JK |
112 | --long:: |
113 | When doing a dry-run, give the output in a the long-format. | |
114 | Implies `--dry-run`. | |
115 | ||
7c9f7038 | 116 | -z:: |
e858af6d | 117 | --null:: |
7c9f7038 JK |
118 | When showing `short` or `porcelain` status output, terminate |
119 | entries in the status output with NUL, instead of LF. If no | |
120 | format is given, implies the `--porcelain` output format. | |
121 | ||
3240240f SB |
122 | -F <file>:: |
123 | --file=<file>:: | |
62033318 JH |
124 | Take the commit message from the given file. Use '-' to |
125 | read the message from the standard input. | |
126 | ||
c4a7ff52 | 127 | --author=<author>:: |
3334729c JS |
128 | Override the commit author. Specify an explicit author using the |
129 | standard `A U Thor <author@example.com>` format. Otherwise <author> | |
130 | is assumed to be a pattern and is used to search for an existing | |
131 | commit by that author (i.e. rev-list --all -i --author=<author>); | |
132 | the commit author is then copied from the first such commit found. | |
130fcca6 | 133 | |
02b47cd7 MV |
134 | --date=<date>:: |
135 | Override the author date used in the commit. | |
136 | ||
3240240f SB |
137 | -m <msg>:: |
138 | --message=<msg>:: | |
62033318 JH |
139 | Use the given <msg> as the commit message. |
140 | ||
3240240f SB |
141 | -t <file>:: |
142 | --template=<file>:: | |
1f08c2c8 JH |
143 | When editing the commit message, start the editor with the |
144 | contents in the given file. The `commit.template` configuration | |
145 | variable is often used to give this option implicitly to the | |
146 | command. This mechanism can be used by projects that want to | |
147 | guide participants with some hints on what to write in the message | |
148 | in what order. If the user exits the editor without editing the | |
149 | message, the commit is aborted. This has no effect when a message | |
150 | is given by other means, e.g. with the `-m` or `-F` options. | |
d1cc130a | 151 | |
3240240f SB |
152 | -s:: |
153 | --signoff:: | |
a0178ae2 | 154 | Add Signed-off-by line by the committer at the end of the commit |
09cff066 | 155 | log message. |
3f971fc4 | 156 | |
3240240f SB |
157 | -n:: |
158 | --no-verify:: | |
aa6da6cd | 159 | This option bypasses the pre-commit and commit-msg hooks. |
6998e4db | 160 | See also linkgit:githooks[5]. |
eaa54efc | 161 | |
36863af1 JH |
162 | --allow-empty:: |
163 | Usually recording a commit that has the exact same tree as its | |
17ef10d0 JH |
164 | sole parent commit is a mistake, and the command prevents you |
165 | from making such a commit. This option bypasses the safety, and | |
6b677a28 | 166 | is primarily for use by foreign SCM interface scripts. |
36863af1 | 167 | |
c9b5fde7 ÆAB |
168 | --allow-empty-message:: |
169 | Like --allow-empty this command is primarily for use by foreign | |
6b677a28 | 170 | SCM interface scripts. It allows you to create a commit with an |
c9b5fde7 ÆAB |
171 | empty commit message without using plumbing commands like |
172 | linkgit:git-commit-tree[1]. | |
173 | ||
5f065737 AR |
174 | --cleanup=<mode>:: |
175 | This option sets how the commit message is cleaned up. | |
176 | The '<mode>' can be one of 'verbatim', 'whitespace', 'strip', | |
177 | and 'default'. The 'default' mode will strip leading and | |
178 | trailing empty lines and #commentary from the commit message | |
179 | only if the message is to be edited. Otherwise only whitespace | |
180 | removed. The 'verbatim' mode does not change message at all, | |
181 | 'whitespace' removes just leading/trailing whitespace lines | |
51fb3a3d RT |
182 | and 'strip' removes both whitespace and commentary. The default |
183 | can be changed by the 'commit.cleanup' configuration variable | |
184 | (see linkgit:git-config[1]). | |
5f065737 | 185 | |
3240240f SB |
186 | -e:: |
187 | --edit:: | |
6d35cc76 JH |
188 | The message taken from file with `-F`, command line with |
189 | `-m`, and from file with `-C` are usually used as the | |
190 | commit log message unmodified. This option lets you | |
191 | further edit the message taken from these sources. | |
192 | ||
ae45320c MM |
193 | --no-edit:: |
194 | Use the selected commit message without launching an editor. | |
195 | For example, `git commit --amend --no-edit` amends a commit | |
196 | without changing its commit message. | |
197 | ||
ae5d8470 | 198 | --amend:: |
ae5d8470 MR |
199 | Used to amend the tip of the current branch. Prepare the tree |
200 | object you would want to replace the latest commit as usual | |
201 | (this includes the usual -i/-o and explicit paths), and the | |
202 | commit log editor is seeded with the commit message from the | |
203 | tip of the current branch. The commit you create replaces the | |
204 | current tip -- if it was a merge, it will have the parents of | |
205 | the current tip as parents -- so the current top commit is | |
206 | discarded. | |
207 | + | |
6cbd5d7d | 208 | -- |
ae5d8470 | 209 | It is a rough equivalent for: |
6cbd5d7d | 210 | ------ |
ae5d8470 MR |
211 | $ git reset --soft HEAD^ |
212 | $ ... do something else to come up with the right tree ... | |
213 | $ git commit -c ORIG_HEAD | |
6cbd5d7d FD |
214 | |
215 | ------ | |
ae5d8470 | 216 | but can be used to amend a merge commit. |
6cbd5d7d | 217 | -- |
97c33c65 TR |
218 | + |
219 | You should understand the implications of rewriting history if you | |
220 | amend a commit that has already been published. (See the "RECOVERING | |
221 | FROM UPSTREAM REBASE" section in linkgit:git-rebase[1].) | |
ae5d8470 | 222 | |
77effefe AS |
223 | --no-post-rewrite:: |
224 | Bypass the post-rewrite hook. | |
225 | ||
3240240f SB |
226 | -i:: |
227 | --include:: | |
6c96753d JH |
228 | Before making a commit out of staged contents so far, |
229 | stage the contents of paths given on the command line | |
230 | as well. This is usually not what you want unless you | |
231 | are concluding a conflicted merge. | |
62033318 | 232 | |
3240240f SB |
233 | -o:: |
234 | --only:: | |
d4ba07ca JS |
235 | Make a commit only from the paths specified on the |
236 | command line, disregarding any contents that have been | |
237 | staged so far. This is the default mode of operation of | |
0b444cdb | 238 | 'git commit' if any paths are given on the command line, |
d4ba07ca JS |
239 | in which case this option can be omitted. |
240 | If this option is specified together with '--amend', then | |
04c8ce9c | 241 | no paths need to be specified, which can be used to amend |
d4ba07ca JS |
242 | the last commit without committing changes that have |
243 | already been staged. | |
244 | ||
1947bdbc JH |
245 | -u[<mode>]:: |
246 | --untracked-files[=<mode>]:: | |
4cc62606 | 247 | Show untracked files. |
4bfee30a | 248 | + |
4cc62606 CB |
249 | The mode parameter is optional (defaults to 'all'), and is used to |
250 | specify the handling of untracked files; when -u is not used, the | |
251 | default is 'normal', i.e. show untracked files and directories. | |
e9e92198 JH |
252 | + |
253 | The possible options are: | |
4bfee30a | 254 | + |
6c2ce048 | 255 | - 'no' - Show no untracked files |
4bfee30a MSO |
256 | - 'normal' - Shows untracked files and directories |
257 | - 'all' - Also shows individual files in untracked directories. | |
d6293d1f | 258 | + |
4cc62606 CB |
259 | The default can be changed using the status.showUntrackedFiles |
260 | configuration variable documented in linkgit:git-config[1]. | |
af83bed6 | 261 | |
3240240f SB |
262 | -v:: |
263 | --verbose:: | |
af83bed6 JN |
264 | Show unified diff between the HEAD commit and what |
265 | would be committed at the bottom of the commit message | |
266 | template. Note that this diff output doesn't have its | |
267 | lines prefixed with '#'. | |
268 | ||
3240240f SB |
269 | -q:: |
270 | --quiet:: | |
23bfbb81 | 271 | Suppress commit summary message. |
ebd124c6 | 272 | |
3a5d13a3 JH |
273 | --dry-run:: |
274 | Do not create a commit, but show a list of paths that are | |
275 | to be committed, paths with local changes that will be left | |
276 | uncommitted and paths that are untracked. | |
277 | ||
bed575e4 JHI |
278 | --status:: |
279 | Include the output of linkgit:git-status[1] in the commit | |
280 | message template when using an editor to prepare the commit | |
281 | message. Defaults to on, but can be used to override | |
282 | configuration variable commit.status. | |
283 | ||
284 | --no-status:: | |
285 | Do not include the output of linkgit:git-status[1] in the | |
286 | commit message template when using an editor to prepare the | |
287 | default commit message. | |
288 | ||
098bbdc3 TJ |
289 | -S[<keyid>]:: |
290 | --gpg-sign[=<keyid>]:: | |
291 | GPG-sign commit. | |
292 | ||
e994004f | 293 | \--:: |
4170a195 JH |
294 | Do not interpret any more arguments as options. |
295 | ||
296 | <file>...:: | |
6c96753d JH |
297 | When files are given on the command line, the command |
298 | commits the contents of the named files, without | |
299 | recording the changes already staged. The contents of | |
300 | these files are also staged for the next commit on top | |
301 | of what have been staged before. | |
3ae854c3 | 302 | |
788070a2 MV |
303 | :git-commit: 1 |
304 | include::date-formats.txt[] | |
3ae854c3 | 305 | |
6c96753d JH |
306 | EXAMPLES |
307 | -------- | |
308 | When recording your own work, the contents of modified files in | |
309 | your working tree are temporarily stored to a staging area | |
0b444cdb | 310 | called the "index" with 'git add'. A file can be |
97e9a221 | 311 | reverted back, only in the index but not in the working tree, |
6cf378f0 | 312 | to that of the last commit with `git reset HEAD -- <file>`, |
0b444cdb | 313 | which effectively reverts 'git add' and prevents the changes to |
97e9a221 JX |
314 | this file from participating in the next commit. After building |
315 | the state to be committed incrementally with these commands, | |
316 | `git commit` (without any pathname parameter) is used to record what | |
6c96753d JH |
317 | has been staged so far. This is the most basic form of the |
318 | command. An example: | |
319 | ||
320 | ------------ | |
321 | $ edit hello.c | |
322 | $ git rm goodbye.c | |
323 | $ git add hello.c | |
324 | $ git commit | |
325 | ------------ | |
326 | ||
6c96753d JH |
327 | Instead of staging files after each individual change, you can |
328 | tell `git commit` to notice the changes to the files whose | |
329 | contents are tracked in | |
330 | your working tree and do corresponding `git add` and `git rm` | |
331 | for you. That is, this example does the same as the earlier | |
332 | example if there is no other change in your working tree: | |
333 | ||
334 | ------------ | |
335 | $ edit hello.c | |
336 | $ rm goodbye.c | |
337 | $ git commit -a | |
338 | ------------ | |
339 | ||
340 | The command `git commit -a` first looks at your working tree, | |
341 | notices that you have modified hello.c and removed goodbye.c, | |
342 | and performs necessary `git add` and `git rm` for you. | |
343 | ||
344 | After staging changes to many files, you can alter the order the | |
345 | changes are recorded in, by giving pathnames to `git commit`. | |
346 | When pathnames are given, the command makes a commit that | |
347 | only records the changes made to the named paths: | |
348 | ||
349 | ------------ | |
350 | $ edit hello.c hello.h | |
351 | $ git add hello.c hello.h | |
352 | $ edit Makefile | |
353 | $ git commit Makefile | |
354 | ------------ | |
355 | ||
356 | This makes a commit that records the modification to `Makefile`. | |
357 | The changes staged for `hello.c` and `hello.h` are not included | |
358 | in the resulting commit. However, their changes are not lost -- | |
359 | they are still staged and merely held back. After the above | |
360 | sequence, if you do: | |
361 | ||
362 | ------------ | |
363 | $ git commit | |
364 | ------------ | |
365 | ||
366 | this second commit would record the changes to `hello.c` and | |
367 | `hello.h` as expected. | |
368 | ||
0b444cdb | 369 | After a merge (initiated by 'git merge' or 'git pull') stops |
483bc4f0 | 370 | because of conflicts, cleanly merged |
6c96753d JH |
371 | paths are already staged to be committed for you, and paths that |
372 | conflicted are left in unmerged state. You would have to first | |
0b444cdb | 373 | check which paths are conflicting with 'git status' |
6c96753d | 374 | and after fixing them manually in your working tree, you would |
0b444cdb | 375 | stage the result as usual with 'git add': |
6c96753d JH |
376 | |
377 | ------------ | |
378 | $ git status | grep unmerged | |
379 | unmerged: hello.c | |
380 | $ edit hello.c | |
381 | $ git add hello.c | |
382 | ------------ | |
383 | ||
384 | After resolving conflicts and staging the result, `git ls-files -u` | |
385 | would stop mentioning the conflicted path. When you are done, | |
386 | run `git commit` to finally record the merge: | |
387 | ||
388 | ------------ | |
389 | $ git commit | |
390 | ------------ | |
391 | ||
392 | As with the case to record your own changes, you can use `-a` | |
393 | option to save typing. One difference is that during a merge | |
394 | resolution, you cannot use `git commit` with pathnames to | |
395 | alter the order the changes are committed, because the merge | |
396 | should be recorded as a single commit. In fact, the command | |
397 | refuses to run when given pathnames (but see `-i` option). | |
398 | ||
399 | ||
5dc7bcc2 JH |
400 | DISCUSSION |
401 | ---------- | |
402 | ||
936f32d3 JH |
403 | Though not required, it's a good idea to begin the commit message |
404 | with a single short (less than 50 character) line summarizing the | |
405 | change, followed by a blank line and then a more thorough description. | |
52ffe995 JW |
406 | The text up to the first blank line in a commit message is treated |
407 | as the commit title, and that title is used throughout git. | |
408 | For example, linkgit:git-format-patch[1] turns a commit into email, and it uses | |
409 | the title on the Subject line and the rest of the commit in the body. | |
936f32d3 | 410 | |
5dc7bcc2 JH |
411 | include::i18n.txt[] |
412 | ||
ef0c2abf AR |
413 | ENVIRONMENT AND CONFIGURATION VARIABLES |
414 | --------------------------------------- | |
415 | The editor used to edit the commit log message will be chosen from the | |
416 | GIT_EDITOR environment variable, the core.editor configuration variable, the | |
417 | VISUAL environment variable, or the EDITOR environment variable (in that | |
b4479f07 | 418 | order). See linkgit:git-var[1] for details. |
6c96753d JH |
419 | |
420 | HOOKS | |
421 | ----- | |
8089c85b | 422 | This command can run `commit-msg`, `prepare-commit-msg`, `pre-commit`, |
6998e4db | 423 | and `post-commit` hooks. See linkgit:githooks[5] for more |
6c96753d | 424 | information. |
130fcca6 | 425 | |
41f597d9 JK |
426 | FILES |
427 | ----- | |
428 | ||
429 | `$GIT_DIR/COMMIT_EDITMSG`:: | |
430 | This file contains the commit message of a commit in progress. | |
431 | If `git commit` exits due to an error before creating a commit, | |
432 | any commit message that has been provided by the user (e.g., in | |
433 | an editor session) will be available in this file, but will be | |
434 | overwritten by the next invocation of `git commit`. | |
130fcca6 | 435 | |
6c96753d JH |
436 | SEE ALSO |
437 | -------- | |
5162e697 DM |
438 | linkgit:git-add[1], |
439 | linkgit:git-rm[1], | |
440 | linkgit:git-mv[1], | |
441 | linkgit:git-merge[1], | |
442 | linkgit:git-commit-tree[1] | |
130fcca6 | 443 | |
62033318 JH |
444 | GIT |
445 | --- | |
9e1f0a85 | 446 | Part of the linkgit:git[1] suite |