]>
Commit | Line | Data |
---|---|---|
dfd66ddf CC |
1 | git-interpret-trailers(1) |
2 | ========================= | |
3 | ||
4 | NAME | |
5 | ---- | |
99e09daf | 6 | git-interpret-trailers - add or parse structured information in commit messages |
dfd66ddf CC |
7 | |
8 | SYNOPSIS | |
9 | -------- | |
10 | [verse] | |
de613050 RD |
11 | 'git interpret-trailers' [<options>] [(--trailer <token>[(=|:)<value>])...] [<file>...] |
12 | 'git interpret-trailers' [<options>] [--parse] [<file>...] | |
dfd66ddf CC |
13 | |
14 | DESCRIPTION | |
15 | ----------- | |
99e09daf | 16 | Help parsing or adding 'trailers' lines, that look similar to RFC 822 e-mail |
dfd66ddf CC |
17 | headers, at the end of the otherwise free-form part of a commit |
18 | message. | |
19 | ||
20 | This command reads some patches or commit messages from either the | |
99e09daf JK |
21 | <file> arguments or the standard input if no <file> is specified. If |
22 | `--parse` is specified, the output consists of the parsed trailers. | |
23 | ||
5a0d0c03 | 24 | Otherwise, this command applies the arguments passed using the |
99e09daf JK |
25 | `--trailer` option, if any, to the commit message part of each input |
26 | file. The result is emitted on the standard output. | |
dfd66ddf CC |
27 | |
28 | Some configuration variables control the way the `--trailer` arguments | |
29 | are applied to each commit message and the way any existing trailer in | |
30 | the commit message is changed. They also make it possible to | |
31 | automatically add some trailers. | |
32 | ||
33 | By default, a '<token>=<value>' or '<token>:<value>' argument given | |
34 | using `--trailer` will be appended after the existing trailers only if | |
35 | the last trailer has a different (<token>, <value>) pair (or if there | |
36 | is no existing trailer). The <token> and <value> parts will be trimmed | |
37 | to remove starting and trailing whitespace, and the resulting trimmed | |
38 | <token> and <value> will appear in the message like this: | |
39 | ||
40 | ------------------------------------------------ | |
41 | token: value | |
42 | ------------------------------------------------ | |
43 | ||
44 | This means that the trimmed <token> and <value> will be separated by | |
45 | `': '` (one colon followed by one space). | |
46 | ||
47 | By default the new trailer will appear at the end of all the existing | |
48 | trailers. If there is no existing trailer, the new trailer will appear | |
f745acb0 | 49 | after the commit message part of the output, and, if there is no line |
dfd66ddf CC |
50 | with only spaces at the end of the commit message part, one blank line |
51 | will be added before the new trailer. | |
52 | ||
53 | Existing trailers are extracted from the input message by looking for | |
760f1ad1 | 54 | a group of one or more lines that (i) is all trailers, or (ii) contains at |
df616b19 JT |
55 | least one Git-generated or user-configured trailer and consists of at |
56 | least 25% trailers. | |
14624506 | 57 | The group must be preceded by one or more empty (or whitespace-only) lines. |
dfd66ddf CC |
58 | The group must either be at the end of the message or be the last |
59 | non-whitespace lines before a line that starts with '---'. Such three | |
60 | minus signs start the patch part of the message. | |
61 | ||
c463a6b2 | 62 | When reading trailers, there can be whitespaces after the |
dfd66ddf | 63 | token, the separator and the value. There can also be whitespaces |
60ef86a1 JT |
64 | inside the token and the value. The value may be split over multiple lines with |
65 | each subsequent line starting with whitespace, like the "folding" in RFC 822. | |
dfd66ddf CC |
66 | |
67 | Note that 'trailers' do not follow and are not intended to follow many | |
60ef86a1 JT |
68 | rules for RFC 822 headers. For example they do not follow |
69 | the encoding rules and probably many other rules. | |
dfd66ddf CC |
70 | |
71 | OPTIONS | |
72 | ------- | |
e1f89863 TK |
73 | --in-place:: |
74 | Edit the files in place. | |
75 | ||
dfd66ddf CC |
76 | --trim-empty:: |
77 | If the <value> part of any trailer contains only whitespace, | |
78 | the whole trailer will be removed from the resulting message. | |
a43eb67e | 79 | This applies to existing trailers as well as new trailers. |
dfd66ddf CC |
80 | |
81 | --trailer <token>[(=|:)<value>]:: | |
82 | Specify a (<token>, <value>) pair that should be applied as a | |
83 | trailer to the input messages. See the description of this | |
84 | command. | |
85 | ||
0ea5292e PB |
86 | --where <placement>:: |
87 | --no-where:: | |
88 | Specify where all new trailers will be added. A setting | |
89 | provided with '--where' overrides all configuration variables | |
90 | and applies to all '--trailer' options until the next occurrence of | |
1e83b9bf SB |
91 | '--where' or '--no-where'. Possible values are `after`, `before`, |
92 | `end` or `start`. | |
0ea5292e PB |
93 | |
94 | --if-exists <action>:: | |
95 | --no-if-exists:: | |
96 | Specify what action will be performed when there is already at | |
97 | least one trailer with the same <token> in the message. A setting | |
98 | provided with '--if-exists' overrides all configuration variables | |
99 | and applies to all '--trailer' options until the next occurrence of | |
1e83b9bf SB |
100 | '--if-exists' or '--no-if-exists'. Possible actions are `addIfDifferent`, |
101 | `addIfDifferentNeighbor`, `add`, `replace` and `doNothing`. | |
0ea5292e PB |
102 | |
103 | --if-missing <action>:: | |
104 | --no-if-missing:: | |
105 | Specify what action will be performed when there is no other | |
106 | trailer with the same <token> in the message. A setting | |
107 | provided with '--if-missing' overrides all configuration variables | |
108 | and applies to all '--trailer' options until the next occurrence of | |
1e83b9bf SB |
109 | '--if-missing' or '--no-if-missing'. Possible actions are `doNothing` |
110 | or `add`. | |
0ea5292e | 111 | |
56c493ed JK |
112 | --only-trailers:: |
113 | Output only the trailers, not any other parts of the input. | |
114 | ||
fdbdb64f JK |
115 | --only-input:: |
116 | Output only trailers that exist in the input; do not add any | |
117 | from the command-line or by following configured `trailer.*` | |
118 | rules. | |
119 | ||
00002396 JK |
120 | --unfold:: |
121 | Remove any whitespace-continuation in trailers, so that each | |
122 | trailer appears on a line by itself with its full content. | |
123 | ||
99e09daf JK |
124 | --parse:: |
125 | A convenience alias for `--only-trailers --only-input | |
126 | --unfold`. | |
127 | ||
dfd66ddf CC |
128 | CONFIGURATION VARIABLES |
129 | ----------------------- | |
130 | ||
131 | trailer.separators:: | |
132 | This option tells which characters are recognized as trailer | |
133 | separators. By default only ':' is recognized as a trailer | |
134 | separator, except that '=' is always accepted on the command | |
135 | line for compatibility with other git commands. | |
136 | + | |
137 | The first character given by this option will be the default character | |
138 | used when another separator is not specified in the config for this | |
139 | trailer. | |
140 | + | |
141 | For example, if the value for this option is "%=$", then only lines | |
142 | using the format '<token><sep><value>' with <sep> containing '%', '=' | |
143 | or '$' and then spaces will be considered trailers. And '%' will be | |
144 | the default separator used, so by default trailers will appear like: | |
145 | '<token>% <value>' (one percent sign and one space will appear between | |
146 | the token and the value). | |
147 | ||
148 | trailer.where:: | |
149 | This option tells where a new trailer will be added. | |
150 | + | |
151 | This can be `end`, which is the default, `start`, `after` or `before`. | |
152 | + | |
153 | If it is `end`, then each new trailer will appear at the end of the | |
154 | existing trailers. | |
155 | + | |
156 | If it is `start`, then each new trailer will appear at the start, | |
157 | instead of the end, of the existing trailers. | |
158 | + | |
159 | If it is `after`, then each new trailer will appear just after the | |
160 | last trailer with the same <token>. | |
161 | + | |
162 | If it is `before`, then each new trailer will appear just before the | |
163 | first trailer with the same <token>. | |
164 | ||
165 | trailer.ifexists:: | |
166 | This option makes it possible to choose what action will be | |
167 | performed when there is already at least one trailer with the | |
168 | same <token> in the message. | |
169 | + | |
170 | The valid values for this option are: `addIfDifferentNeighbor` (this | |
b275da81 | 171 | is the default), `addIfDifferent`, `add`, `replace` or `doNothing`. |
dfd66ddf CC |
172 | + |
173 | With `addIfDifferentNeighbor`, a new trailer will be added only if no | |
174 | trailer with the same (<token>, <value>) pair is above or below the line | |
175 | where the new trailer will be added. | |
176 | + | |
177 | With `addIfDifferent`, a new trailer will be added only if no trailer | |
178 | with the same (<token>, <value>) pair is already in the message. | |
179 | + | |
180 | With `add`, a new trailer will be added, even if some trailers with | |
181 | the same (<token>, <value>) pair are already in the message. | |
182 | + | |
183 | With `replace`, an existing trailer with the same <token> will be | |
184 | deleted and the new trailer will be added. The deleted trailer will be | |
185 | the closest one (with the same <token>) to the place where the new one | |
186 | will be added. | |
187 | + | |
188 | With `doNothing`, nothing will be done; that is no new trailer will be | |
189 | added if there is already one with the same <token> in the message. | |
190 | ||
191 | trailer.ifmissing:: | |
192 | This option makes it possible to choose what action will be | |
193 | performed when there is not yet any trailer with the same | |
194 | <token> in the message. | |
195 | + | |
196 | The valid values for this option are: `add` (this is the default) and | |
197 | `doNothing`. | |
198 | + | |
199 | With `add`, a new trailer will be added. | |
200 | + | |
201 | With `doNothing`, nothing will be done. | |
202 | ||
203 | trailer.<token>.key:: | |
204 | This `key` will be used instead of <token> in the trailer. At | |
205 | the end of this key, a separator can appear and then some | |
206 | space characters. By default the only valid separator is ':', | |
207 | but this can be changed using the `trailer.separators` config | |
208 | variable. | |
209 | + | |
210 | If there is a separator, then the key will be used instead of both the | |
211 | <token> and the default separator when adding the trailer. | |
212 | ||
213 | trailer.<token>.where:: | |
214 | This option takes the same values as the 'trailer.where' | |
215 | configuration variable and it overrides what is specified by | |
216 | that option for trailers with the specified <token>. | |
217 | ||
c88bf543 PB |
218 | trailer.<token>.ifexists:: |
219 | This option takes the same values as the 'trailer.ifexists' | |
dfd66ddf CC |
220 | configuration variable and it overrides what is specified by |
221 | that option for trailers with the specified <token>. | |
222 | ||
223 | trailer.<token>.ifmissing:: | |
224 | This option takes the same values as the 'trailer.ifmissing' | |
225 | configuration variable and it overrides what is specified by | |
226 | that option for trailers with the specified <token>. | |
227 | ||
228 | trailer.<token>.command:: | |
229 | This option can be used to specify a shell command that will | |
230 | be called to automatically add or modify a trailer with the | |
231 | specified <token>. | |
232 | + | |
233 | When this option is specified, the behavior is as if a special | |
234 | '<token>=<value>' argument were added at the beginning of the command | |
235 | line, where <value> is taken to be the standard output of the | |
236 | specified command with any leading and trailing whitespace trimmed | |
237 | off. | |
238 | + | |
239 | If the command contains the `$ARG` string, this string will be | |
240 | replaced with the <value> part of an existing trailer with the same | |
241 | <token>, if any, before the command is launched. | |
242 | + | |
243 | If some '<token>=<value>' arguments are also passed on the command | |
244 | line, when a 'trailer.<token>.command' is configured, the command will | |
245 | also be executed for each of these arguments. And the <value> part of | |
246 | these arguments, if any, will be used to replace the `$ARG` string in | |
247 | the command. | |
248 | ||
249 | EXAMPLES | |
250 | -------- | |
251 | ||
252 | * Configure a 'sign' trailer with a 'Signed-off-by' key, and then | |
253 | add two of these trailers to a message: | |
254 | + | |
255 | ------------ | |
256 | $ git config trailer.sign.key "Signed-off-by" | |
257 | $ cat msg.txt | |
258 | subject | |
259 | ||
260 | message | |
261 | $ cat msg.txt | git interpret-trailers --trailer 'sign: Alice <alice@example.com>' --trailer 'sign: Bob <bob@example.com>' | |
262 | subject | |
263 | ||
264 | message | |
265 | ||
266 | Signed-off-by: Alice <alice@example.com> | |
267 | Signed-off-by: Bob <bob@example.com> | |
268 | ------------ | |
269 | ||
bcf9626a | 270 | * Use the `--in-place` option to edit a message file in place: |
e1f89863 TK |
271 | + |
272 | ------------ | |
273 | $ cat msg.txt | |
274 | subject | |
275 | ||
276 | message | |
277 | ||
278 | Signed-off-by: Bob <bob@example.com> | |
279 | $ git interpret-trailers --trailer 'Acked-by: Alice <alice@example.com>' --in-place msg.txt | |
280 | $ cat msg.txt | |
281 | subject | |
282 | ||
283 | message | |
284 | ||
285 | Signed-off-by: Bob <bob@example.com> | |
286 | Acked-by: Alice <alice@example.com> | |
287 | ------------ | |
288 | ||
dfd66ddf CC |
289 | * Extract the last commit as a patch, and add a 'Cc' and a |
290 | 'Reviewed-by' trailer to it: | |
291 | + | |
292 | ------------ | |
293 | $ git format-patch -1 | |
294 | 0001-foo.patch | |
295 | $ git interpret-trailers --trailer 'Cc: Alice <alice@example.com>' --trailer 'Reviewed-by: Bob <bob@example.com>' 0001-foo.patch >0001-bar.patch | |
296 | ------------ | |
297 | ||
298 | * Configure a 'sign' trailer with a command to automatically add a | |
299 | 'Signed-off-by: ' with the author information only if there is no | |
300 | 'Signed-off-by: ' already, and show how it works: | |
301 | + | |
302 | ------------ | |
303 | $ git config trailer.sign.key "Signed-off-by: " | |
304 | $ git config trailer.sign.ifmissing add | |
305 | $ git config trailer.sign.ifexists doNothing | |
306 | $ git config trailer.sign.command 'echo "$(git config user.name) <$(git config user.email)>"' | |
307 | $ git interpret-trailers <<EOF | |
308 | > EOF | |
309 | ||
310 | Signed-off-by: Bob <bob@example.com> | |
311 | $ git interpret-trailers <<EOF | |
312 | > Signed-off-by: Alice <alice@example.com> | |
313 | > EOF | |
314 | ||
315 | Signed-off-by: Alice <alice@example.com> | |
316 | ------------ | |
317 | ||
318 | * Configure a 'fix' trailer with a key that contains a '#' and no | |
319 | space after this character, and show how it works: | |
320 | + | |
321 | ------------ | |
322 | $ git config trailer.separators ":#" | |
323 | $ git config trailer.fix.key "Fix #" | |
324 | $ echo "subject" | git interpret-trailers --trailer fix=42 | |
325 | subject | |
326 | ||
327 | Fix #42 | |
328 | ------------ | |
329 | ||
330 | * Configure a 'see' trailer with a command to show the subject of a | |
331 | commit that is related, and show how it works: | |
332 | + | |
333 | ------------ | |
334 | $ git config trailer.see.key "See-also: " | |
335 | $ git config trailer.see.ifExists "replace" | |
336 | $ git config trailer.see.ifMissing "doNothing" | |
337 | $ git config trailer.see.command "git log -1 --oneline --format=\"%h (%s)\" --abbrev-commit --abbrev=14 \$ARG" | |
338 | $ git interpret-trailers <<EOF | |
339 | > subject | |
340 | > | |
341 | > message | |
342 | > | |
343 | > see: HEAD~2 | |
344 | > EOF | |
345 | subject | |
346 | ||
347 | message | |
348 | ||
349 | See-also: fe3187489d69c4 (subject of related commit) | |
350 | ------------ | |
351 | ||
352 | * Configure a commit template with some trailers with empty values | |
353 | (using sed to show and keep the trailing spaces at the end of the | |
354 | trailers), then configure a commit-msg hook that uses | |
355 | 'git interpret-trailers' to remove trailers with empty values and | |
356 | to add a 'git-version' trailer: | |
357 | + | |
358 | ------------ | |
359 | $ sed -e 's/ Z$/ /' >commit_template.txt <<EOF | |
360 | > ***subject*** | |
361 | > | |
362 | > ***message*** | |
363 | > | |
364 | > Fixes: Z | |
365 | > Cc: Z | |
366 | > Reviewed-by: Z | |
367 | > Signed-off-by: Z | |
368 | > EOF | |
369 | $ git config commit.template commit_template.txt | |
370 | $ cat >.git/hooks/commit-msg <<EOF | |
371 | > #!/bin/sh | |
372 | > git interpret-trailers --trim-empty --trailer "git-version: \$(git describe)" "\$1" > "\$1.new" | |
373 | > mv "\$1.new" "\$1" | |
374 | > EOF | |
375 | $ chmod +x .git/hooks/commit-msg | |
376 | ------------ | |
377 | ||
378 | SEE ALSO | |
379 | -------- | |
380 | linkgit:git-commit[1], linkgit:git-format-patch[1], linkgit:git-config[1] | |
381 | ||
382 | GIT | |
383 | --- | |
384 | Part of the linkgit:git[1] suite |