6 git-for-each-ref - Output information on each ref
11 'git for-each-ref' [--count=<count>] [--shell|--perl|--python|--tcl]
12 [(--sort=<key>)...] [--format=<format>] [<pattern>...]
13 [--points-at <object>]
18 Iterate over all refs that match `<pattern>` and show them
19 according to the given `<format>`, after sorting them according
20 to the given set of `<key>`. If `<count>` is given, stop after
21 showing that many refs. The interpolated values in `<format>`
22 can optionally be quoted as string literals in the specified
23 host language allowing their direct evaluation in that language.
28 By default the command shows all refs that match
29 `<pattern>`. This option makes it stop after showing
33 A field name to sort on. Prefix `-` to sort in
34 descending order of the value. When unspecified,
35 `refname` is used. You may use the --sort=<key> option
36 multiple times, in which case the last key becomes the primary
40 A string that interpolates `%(fieldname)` from the
41 object pointed at by a ref being shown. If `fieldname`
42 is prefixed with an asterisk (`*`) and the ref points
43 at a tag object, the value for the field in the object
44 tag refers is used. When unspecified, defaults to
45 `%(objectname) SPC %(objecttype) TAB %(refname)`.
46 It also interpolates `%%` to `%`, and `%xx` where `xx`
47 are hex digits interpolates to character with hex code
48 `xx`; for example `%00` interpolates to `\0` (NUL),
49 `%09` to `\t` (TAB) and `%0a` to `\n` (LF).
52 If one or more patterns are given, only refs are shown that
53 match against at least one pattern, either using fnmatch(3) or
54 literally, in the latter case matching completely or from the
55 beginning up to a slash.
61 If given, strings that substitute `%(fieldname)`
62 placeholders are quoted as string literals suitable for
63 the specified host language. This is meant to produce
64 a scriptlet that can directly be `eval`ed.
66 --points-at <object>::
67 Only list refs which points at the given object.
72 Various values from structured fields in referenced objects can
73 be used to interpolate into the resulting output, or as sort
76 For all objects, the following names can be used:
79 The name of the ref (the part after $GIT_DIR/).
80 For a non-ambiguous short name of the ref append `:short`.
81 The option core.warnAmbiguousRefs is used to select the strict
85 The type of the object (`blob`, `tree`, `commit`, `tag`).
88 The size of the object (the same as 'git cat-file -s' reports).
91 The object name (aka SHA-1).
92 For a non-ambiguous abbreviation of the object name append `:short`.
95 The name of a local ref which can be considered ``upstream''
96 from the displayed ref. Respects `:short` in the same way as
97 `refname` above. Additionally respects `:track` to show
98 "[ahead N, behind M]" and `:trackshort` to show the terse
99 version: ">" (ahead), "<" (behind), "<>" (ahead and behind),
100 or "=" (in sync). Has no effect if the ref does not have
101 tracking information associated with it.
104 The name of a local ref which represents the `@{push}` location
105 for the displayed ref. Respects `:short`, `:track`, and
106 `:trackshort` options as `upstream` does. Produces an empty
107 string if no `@{push}` ref is configured.
110 '*' if HEAD matches current ref (the checked out branch), ' '
114 Change output color. Followed by `:<colorname>`, where names
115 are described in `color.branch.*`.
117 In addition to the above, for commit and tag objects, the header
118 field names (`tree`, `parent`, `object`, `type`, and `tag`) can
119 be used to specify the value in the header field.
121 Fields that have name-email-date tuple as its value (`author`,
122 `committer`, and `tagger`) can be suffixed with `name`, `email`,
123 and `date` to extract the named component.
125 The complete message in a commit and tag object is `contents`.
126 Its first line is `contents:subject`, where subject is the concatenation
127 of all lines of the commit message up to the first blank line. The next
128 line is 'contents:body', where body is all of the lines after the first
129 blank line. Finally, the optional GPG signature is `contents:signature`.
131 For sorting purposes, fields with numeric values sort in numeric
132 order (`objectsize`, `authordate`, `committerdate`, `taggerdate`).
133 All other fields are used to sort in their byte-value order.
135 In any case, a field name that refers to a field inapplicable to
136 the object referred by the ref does not cause an error. It
137 returns an empty string instead.
139 As a special case for the date-type fields, you may specify a format for
140 the date by adding one of `:default`, `:relative`, `:short`, `:local`,
141 `:iso8601`, `:rfc2822` or `:raw` to the end of the fieldname; e.g.
142 `%(taggerdate:relative)`.
148 An example directly producing formatted text. Show the most recent
154 git for-each-ref --count=3 --sort='-*authordate' \
155 --format='From: %(*authorname) %(*authoremail)
165 A simple example showing the use of shell eval on the output,
166 demonstrating the use of --shell. List the prefixes of all heads:
170 git for-each-ref --shell --format="ref=%(refname)" refs/heads | \
179 A bit more elaborate report on tags, demonstrating that the format
180 may be an entire script:
199 # could be a lightweight tag
201 kind="Lightweight tag"
209 echo "$kind $T points at a $t object $o"
210 if test "z$t" = zcommit
212 echo "The commit was authored by $n $e
217 Its message reads as:
219 echo "$b" | sed -e "s/^/ /"
224 eval=`git for-each-ref --shell --format="$fmt" \
225 --sort='*objecttype' \
233 linkgit:git-show-ref[1]
237 Part of the linkgit:git[1] suite