]>
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] |
3a5d13a3 | 11 | 'git commit' [-a | --interactive] [-s] [-v] [-u<mode>] [--amend] [--dry-run] |
60c2993c | 12 | [(-c | -C) <commit>] [-F <file> | -m <msg>] [--dry-run] |
c4a7ff52 | 13 | [--allow-empty] [--no-verify] [-e] [--author=<author>] |
5f065737 | 14 | [--cleanup=<mode>] [--] [[-i | -o ]<file>...] |
62033318 JH |
15 | |
16 | DESCRIPTION | |
17 | ----------- | |
d69806d1 JN |
18 | Stores the current contents of the index in a new commit along |
19 | with a log message from the user describing the changes. | |
62033318 | 20 | |
a76c2acb | 21 | The content to be added can be specified in several ways: |
f9935bf9 | 22 | |
ba020ef5 | 23 | 1. by using 'git-add' to incrementally "add" changes to the |
a76c2acb | 24 | index before using the 'commit' command (Note: even modified |
6c96753d | 25 | files must be "added"); |
5bfc4f23 | 26 | |
ba020ef5 | 27 | 2. by using 'git-rm' to remove files from the working tree |
a76c2acb | 28 | and the index, again before using the 'commit' command; |
6c96753d | 29 | |
a76c2acb BF |
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 | |
6fc4a7e5 MB |
32 | record the current content of the listed files (which must already |
33 | be known to git); | |
6c96753d | 34 | |
a76c2acb BF |
35 | 4. by using the -a switch with the 'commit' command to automatically |
36 | "add" changes from all known files (i.e. all files that are already | |
37 | listed in the index) and to automatically "rm" files in the index | |
38 | that have been removed from the working tree, and then perform the | |
39 | actual commit; | |
6c96753d | 40 | |
6cbf07ef PB |
41 | 5. by using the --interactive switch with the 'commit' command to decide one |
42 | by one which files should be part of the commit, before finalizing the | |
ba020ef5 | 43 | operation. Currently, this is done by invoking 'git-add --interactive'. |
6cbf07ef | 44 | |
60c2993c | 45 | The `--dry-run` option can be used to obtain a |
6c96753d | 46 | summary of what is included by any of the above for the next |
60c2993c | 47 | commit by giving the same set of parameters (options and paths). |
6c96753d | 48 | |
483bc4f0 | 49 | If you make a commit and then find a mistake immediately after |
ba020ef5 | 50 | that, you can recover from it with 'git-reset'. |
5bfc4f23 | 51 | |
6d35cc76 | 52 | |
62033318 JH |
53 | OPTIONS |
54 | ------- | |
3240240f SB |
55 | -a:: |
56 | --all:: | |
6c96753d JH |
57 | Tell the command to automatically stage files that have |
58 | been modified and deleted, but new files you have not | |
59 | told git about are not affected. | |
62033318 | 60 | |
3240240f SB |
61 | -C <commit>:: |
62 | --reuse-message=<commit>:: | |
bc47c29e | 63 | Take an existing commit object, and reuse the log message |
62033318 | 64 | and the authorship information (including the timestamp) |
bc47c29e | 65 | when creating the commit. |
62033318 | 66 | |
3240240f SB |
67 | -c <commit>:: |
68 | --reedit-message=<commit>:: | |
bc47c29e SB |
69 | Like '-C', but with '-c' the editor is invoked, so that |
70 | the user can further edit the commit message. | |
71 | ||
60c2993c JH |
72 | --dry-run:: |
73 | Do not actually make a commit, but show the list of paths | |
74 | with updates in the index, paths with changes in the work tree, | |
75 | and paths that are untracked, similar to the one that is given | |
76 | in the commit log editor. | |
77 | ||
3240240f SB |
78 | -F <file>:: |
79 | --file=<file>:: | |
62033318 JH |
80 | Take the commit message from the given file. Use '-' to |
81 | read the message from the standard input. | |
82 | ||
c4a7ff52 | 83 | --author=<author>:: |
146ea068 JH |
84 | Override the author name used in the commit. You can use the |
85 | standard `A U Thor <author@example.com>` format. Otherwise, | |
86 | an existing commit that matches the given string and its author | |
87 | name is used. | |
130fcca6 | 88 | |
3240240f SB |
89 | -m <msg>:: |
90 | --message=<msg>:: | |
62033318 JH |
91 | Use the given <msg> as the commit message. |
92 | ||
3240240f SB |
93 | -t <file>:: |
94 | --template=<file>:: | |
d1cc130a SG |
95 | Use the contents of the given file as the initial version |
96 | of the commit message. The editor is invoked and you can | |
97 | make subsequent changes. If a message is specified using | |
383e45ce BG |
98 | the `-m` or `-F` options, this option has no effect. This |
99 | overrides the `commit.template` configuration variable. | |
d1cc130a | 100 | |
3240240f SB |
101 | -s:: |
102 | --signoff:: | |
a0178ae2 | 103 | Add Signed-off-by line by the committer at the end of the commit |
09cff066 | 104 | log message. |
3f971fc4 | 105 | |
3240240f SB |
106 | -n:: |
107 | --no-verify:: | |
aa6da6cd | 108 | This option bypasses the pre-commit and commit-msg hooks. |
6998e4db | 109 | See also linkgit:githooks[5]. |
eaa54efc | 110 | |
36863af1 JH |
111 | --allow-empty:: |
112 | Usually recording a commit that has the exact same tree as its | |
17ef10d0 JH |
113 | sole parent commit is a mistake, and the command prevents you |
114 | from making such a commit. This option bypasses the safety, and | |
115 | is primarily for use by foreign scm interface scripts. | |
36863af1 | 116 | |
5f065737 AR |
117 | --cleanup=<mode>:: |
118 | This option sets how the commit message is cleaned up. | |
119 | The '<mode>' can be one of 'verbatim', 'whitespace', 'strip', | |
120 | and 'default'. The 'default' mode will strip leading and | |
121 | trailing empty lines and #commentary from the commit message | |
122 | only if the message is to be edited. Otherwise only whitespace | |
123 | removed. The 'verbatim' mode does not change message at all, | |
124 | 'whitespace' removes just leading/trailing whitespace lines | |
125 | and 'strip' removes both whitespace and commentary. | |
126 | ||
3240240f SB |
127 | -e:: |
128 | --edit:: | |
6d35cc76 JH |
129 | The message taken from file with `-F`, command line with |
130 | `-m`, and from file with `-C` are usually used as the | |
131 | commit log message unmodified. This option lets you | |
132 | further edit the message taken from these sources. | |
133 | ||
ae5d8470 | 134 | --amend:: |
ae5d8470 MR |
135 | Used to amend the tip of the current branch. Prepare the tree |
136 | object you would want to replace the latest commit as usual | |
137 | (this includes the usual -i/-o and explicit paths), and the | |
138 | commit log editor is seeded with the commit message from the | |
139 | tip of the current branch. The commit you create replaces the | |
140 | current tip -- if it was a merge, it will have the parents of | |
141 | the current tip as parents -- so the current top commit is | |
142 | discarded. | |
143 | + | |
6cbd5d7d | 144 | -- |
ae5d8470 | 145 | It is a rough equivalent for: |
6cbd5d7d | 146 | ------ |
ae5d8470 MR |
147 | $ git reset --soft HEAD^ |
148 | $ ... do something else to come up with the right tree ... | |
149 | $ git commit -c ORIG_HEAD | |
6cbd5d7d FD |
150 | |
151 | ------ | |
ae5d8470 | 152 | but can be used to amend a merge commit. |
6cbd5d7d | 153 | -- |
97c33c65 TR |
154 | + |
155 | You should understand the implications of rewriting history if you | |
156 | amend a commit that has already been published. (See the "RECOVERING | |
157 | FROM UPSTREAM REBASE" section in linkgit:git-rebase[1].) | |
ae5d8470 | 158 | |
3240240f SB |
159 | -i:: |
160 | --include:: | |
6c96753d JH |
161 | Before making a commit out of staged contents so far, |
162 | stage the contents of paths given on the command line | |
163 | as well. This is usually not what you want unless you | |
164 | are concluding a conflicted merge. | |
62033318 | 165 | |
3240240f SB |
166 | -o:: |
167 | --only:: | |
d4ba07ca JS |
168 | Make a commit only from the paths specified on the |
169 | command line, disregarding any contents that have been | |
170 | staged so far. This is the default mode of operation of | |
467c0197 | 171 | 'git-commit' if any paths are given on the command line, |
d4ba07ca JS |
172 | in which case this option can be omitted. |
173 | If this option is specified together with '--amend', then | |
04c8ce9c | 174 | no paths need to be specified, which can be used to amend |
d4ba07ca JS |
175 | the last commit without committing changes that have |
176 | already been staged. | |
177 | ||
1947bdbc JH |
178 | -u[<mode>]:: |
179 | --untracked-files[=<mode>]:: | |
4bfee30a MSO |
180 | Show untracked files (Default: 'all'). |
181 | + | |
182 | The mode parameter is optional, and is used to specify | |
183 | the handling of untracked files. The possible options are: | |
184 | + | |
185 | -- | |
6c2ce048 | 186 | - 'no' - Show no untracked files |
4bfee30a MSO |
187 | - 'normal' - Shows untracked files and directories |
188 | - 'all' - Also shows individual files in untracked directories. | |
189 | -- | |
d6293d1f MSO |
190 | + |
191 | See linkgit:git-config[1] for configuration variable | |
192 | used to change the default for when the option is not | |
193 | specified. | |
af83bed6 | 194 | |
3240240f SB |
195 | -v:: |
196 | --verbose:: | |
af83bed6 JN |
197 | Show unified diff between the HEAD commit and what |
198 | would be committed at the bottom of the commit message | |
199 | template. Note that this diff output doesn't have its | |
200 | lines prefixed with '#'. | |
201 | ||
3240240f SB |
202 | -q:: |
203 | --quiet:: | |
23bfbb81 | 204 | Suppress commit summary message. |
ebd124c6 | 205 | |
3a5d13a3 JH |
206 | --dry-run:: |
207 | Do not create a commit, but show a list of paths that are | |
208 | to be committed, paths with local changes that will be left | |
209 | uncommitted and paths that are untracked. | |
210 | ||
e994004f | 211 | \--:: |
4170a195 JH |
212 | Do not interpret any more arguments as options. |
213 | ||
214 | <file>...:: | |
6c96753d JH |
215 | When files are given on the command line, the command |
216 | commits the contents of the named files, without | |
217 | recording the changes already staged. The contents of | |
218 | these files are also staged for the next commit on top | |
219 | of what have been staged before. | |
3ae854c3 JH |
220 | |
221 | ||
6c96753d JH |
222 | EXAMPLES |
223 | -------- | |
224 | When recording your own work, the contents of modified files in | |
225 | your working tree are temporarily stored to a staging area | |
ba020ef5 | 226 | called the "index" with 'git-add'. A file can be |
97e9a221 | 227 | reverted back, only in the index but not in the working tree, |
b1889c36 | 228 | to that of the last commit with `git reset HEAD -- <file>`, |
ba020ef5 | 229 | which effectively reverts 'git-add' and prevents the changes to |
97e9a221 JX |
230 | this file from participating in the next commit. After building |
231 | the state to be committed incrementally with these commands, | |
232 | `git commit` (without any pathname parameter) is used to record what | |
6c96753d JH |
233 | has been staged so far. This is the most basic form of the |
234 | command. An example: | |
235 | ||
236 | ------------ | |
237 | $ edit hello.c | |
238 | $ git rm goodbye.c | |
239 | $ git add hello.c | |
240 | $ git commit | |
241 | ------------ | |
242 | ||
6c96753d JH |
243 | Instead of staging files after each individual change, you can |
244 | tell `git commit` to notice the changes to the files whose | |
245 | contents are tracked in | |
246 | your working tree and do corresponding `git add` and `git rm` | |
247 | for you. That is, this example does the same as the earlier | |
248 | example if there is no other change in your working tree: | |
249 | ||
250 | ------------ | |
251 | $ edit hello.c | |
252 | $ rm goodbye.c | |
253 | $ git commit -a | |
254 | ------------ | |
255 | ||
256 | The command `git commit -a` first looks at your working tree, | |
257 | notices that you have modified hello.c and removed goodbye.c, | |
258 | and performs necessary `git add` and `git rm` for you. | |
259 | ||
260 | After staging changes to many files, you can alter the order the | |
261 | changes are recorded in, by giving pathnames to `git commit`. | |
262 | When pathnames are given, the command makes a commit that | |
263 | only records the changes made to the named paths: | |
264 | ||
265 | ------------ | |
266 | $ edit hello.c hello.h | |
267 | $ git add hello.c hello.h | |
268 | $ edit Makefile | |
269 | $ git commit Makefile | |
270 | ------------ | |
271 | ||
272 | This makes a commit that records the modification to `Makefile`. | |
273 | The changes staged for `hello.c` and `hello.h` are not included | |
274 | in the resulting commit. However, their changes are not lost -- | |
275 | they are still staged and merely held back. After the above | |
276 | sequence, if you do: | |
277 | ||
278 | ------------ | |
279 | $ git commit | |
280 | ------------ | |
281 | ||
282 | this second commit would record the changes to `hello.c` and | |
283 | `hello.h` as expected. | |
284 | ||
ba020ef5 | 285 | After a merge (initiated by 'git-merge' or 'git-pull') stops |
483bc4f0 | 286 | because of conflicts, cleanly merged |
6c96753d JH |
287 | paths are already staged to be committed for you, and paths that |
288 | conflicted are left in unmerged state. You would have to first | |
ba020ef5 | 289 | check which paths are conflicting with 'git-status' |
6c96753d | 290 | and after fixing them manually in your working tree, you would |
ba020ef5 | 291 | stage the result as usual with 'git-add': |
6c96753d JH |
292 | |
293 | ------------ | |
294 | $ git status | grep unmerged | |
295 | unmerged: hello.c | |
296 | $ edit hello.c | |
297 | $ git add hello.c | |
298 | ------------ | |
299 | ||
300 | After resolving conflicts and staging the result, `git ls-files -u` | |
301 | would stop mentioning the conflicted path. When you are done, | |
302 | run `git commit` to finally record the merge: | |
303 | ||
304 | ------------ | |
305 | $ git commit | |
306 | ------------ | |
307 | ||
308 | As with the case to record your own changes, you can use `-a` | |
309 | option to save typing. One difference is that during a merge | |
310 | resolution, you cannot use `git commit` with pathnames to | |
311 | alter the order the changes are committed, because the merge | |
312 | should be recorded as a single commit. In fact, the command | |
313 | refuses to run when given pathnames (but see `-i` option). | |
314 | ||
315 | ||
5dc7bcc2 JH |
316 | DISCUSSION |
317 | ---------- | |
318 | ||
936f32d3 JH |
319 | Though not required, it's a good idea to begin the commit message |
320 | with a single short (less than 50 character) line summarizing the | |
321 | change, followed by a blank line and then a more thorough description. | |
322 | Tools that turn commits into email, for example, use the first line | |
323 | on the Subject: line and the rest of the commit in the body. | |
324 | ||
5dc7bcc2 JH |
325 | include::i18n.txt[] |
326 | ||
ef0c2abf AR |
327 | ENVIRONMENT AND CONFIGURATION VARIABLES |
328 | --------------------------------------- | |
329 | The editor used to edit the commit log message will be chosen from the | |
330 | GIT_EDITOR environment variable, the core.editor configuration variable, the | |
331 | VISUAL environment variable, or the EDITOR environment variable (in that | |
332 | order). | |
6c96753d JH |
333 | |
334 | HOOKS | |
335 | ----- | |
8089c85b | 336 | This command can run `commit-msg`, `prepare-commit-msg`, `pre-commit`, |
6998e4db | 337 | and `post-commit` hooks. See linkgit:githooks[5] for more |
6c96753d | 338 | information. |
130fcca6 | 339 | |
130fcca6 | 340 | |
6c96753d JH |
341 | SEE ALSO |
342 | -------- | |
5162e697 DM |
343 | linkgit:git-add[1], |
344 | linkgit:git-rm[1], | |
345 | linkgit:git-mv[1], | |
346 | linkgit:git-merge[1], | |
347 | linkgit:git-commit-tree[1] | |
130fcca6 | 348 | |
62033318 JH |
349 | Author |
350 | ------ | |
3f971fc4 | 351 | Written by Linus Torvalds <torvalds@osdl.org> and |
59eb68aa | 352 | Junio C Hamano <gitster@pobox.com> |
3f971fc4 | 353 | |
62033318 JH |
354 | |
355 | GIT | |
356 | --- | |
9e1f0a85 | 357 | Part of the linkgit:git[1] suite |