1git-for-each-ref(1) 2=================== 3 4NAME 5---- 6git-for-each-ref - Output information on each ref 7 8SYNOPSIS 9-------- 10[verse] 11'git for-each-ref' [--count=<count>] [--shell|--perl|--python|--tcl] 12 [(--sort=<key>)...] [--format=<format>] [<pattern>...] 13 [--points-at <object>] [(--merged | --no-merged) [<object>]] 14 [--contains [<object>]] 15 16DESCRIPTION 17----------- 18 19Iterate over all refs that match `<pattern>` and show them 20according to the given `<format>`, after sorting them according 21to the given set of `<key>`. If `<count>` is given, stop after 22showing that many refs. The interpolated values in `<format>` 23can optionally be quoted as string literals in the specified 24host language allowing their direct evaluation in that language. 25 26OPTIONS 27------- 28<count>:: 29 By default the command shows all refs that match 30 `<pattern>`. This option makes it stop after showing 31 that many refs. 32 33<key>:: 34 A field name to sort on. Prefix `-` to sort in 35 descending order of the value. When unspecified, 36 `refname` is used. You may use the --sort=<key> option 37 multiple times, in which case the last key becomes the primary 38 key. 39 40<format>:: 41 A string that interpolates `%(fieldname)` from the 42 object pointed at by a ref being shown. If `fieldname` 43 is prefixed with an asterisk (`*`) and the ref points 44 at a tag object, the value for the field in the object 45 tag refers is used. When unspecified, defaults to 46 `%(objectname) SPC %(objecttype) TAB %(refname)`. 47 It also interpolates `%%` to `%`, and `%xx` where `xx` 48 are hex digits interpolates to character with hex code 49 `xx`; for example `%00` interpolates to `\0` (NUL), 50 `%09` to `\t` (TAB) and `%0a` to `\n` (LF). 51 52<pattern>...:: 53 If one or more patterns are given, only refs are shown that 54 match against at least one pattern, either using fnmatch(3) or 55 literally, in the latter case matching completely or from the 56 beginning up to a slash. 57 58--shell:: 59--perl:: 60--python:: 61--tcl:: 62 If given, strings that substitute `%(fieldname)` 63 placeholders are quoted as string literals suitable for 64 the specified host language. This is meant to produce 65 a scriptlet that can directly be `eval`ed. 66 67--points-at <object>:: 68 Only list refs which points at the given object. 69 70--merged [<object>]:: 71 Only list refs whose tips are reachable from the 72 specified commit (HEAD if not specified). 73 74--no-merged [<object>]:: 75 Only list refs whose tips are not reachable from the 76 specified commit (HEAD if not specified). 77 78--contains [<object>]:: 79 Only list refs which contain the specified commit (HEAD if not 80 specified). 81 82--ignore-case:: 83 Sorting and filtering refs are case insensitive. 84 85FIELD NAMES 86----------- 87 88Various values from structured fields in referenced objects can 89be used to interpolate into the resulting output, or as sort 90keys. 91 92For all objects, the following names can be used: 93 94refname:: 95 The name of the ref (the part after $GIT_DIR/). 96 For a non-ambiguous short name of the ref append `:short`. 97 The option core.warnAmbiguousRefs is used to select the strict 98 abbreviation mode. If `strip=<N>` is appended, strips `<N>` 99 slash-separated path components from the front of the refname 100 (e.g., `%(refname:strip=2)` turns `refs/tags/foo` into `foo`. 101 `<N>` must be a positive integer. If a displayed ref has fewer 102 components than `<N>`, the command aborts with an error. 103 104objecttype:: 105 The type of the object (`blob`, `tree`, `commit`, `tag`). 106 107objectsize:: 108 The size of the object (the same as 'git cat-file -s' reports). 109 110objectname:: 111 The object name (aka SHA-1). 112 For a non-ambiguous abbreviation of the object name append `:short`. 113 For an abbreviation of the object name with desired length append 114 `:short=<length>`, where the minimum length is MINIMUM_ABBREV. The 115 length may be exceeded to ensure unique object names. 116 117upstream:: 118 The name of a local ref which can be considered ``upstream'' 119 from the displayed ref. Respects `:short` in the same way as 120 `refname` above. Additionally respects `:track` to show 121 "[ahead N, behind M]" and `:trackshort` to show the terse 122 version: ">" (ahead), "<" (behind), "<>" (ahead and behind), 123 or "=" (in sync). `:track` also prints "[gone]" whenever 124 unknown upstream ref is encountered. Append `:track,nobracket` 125 to show tracking information without brackets (i.e "ahead N, 126 behind M"). Has no effect if the ref does not have tracking 127 information associated with it. All the options apart from 128 `nobracket` are mutually exclusive, but if used together the 129 last option is selected. 130 131push:: 132 The name of a local ref which represents the `@{push}` location 133 for the displayed ref. Respects `:short`, `:track`, and 134 `:trackshort` options as `upstream` does. Produces an empty 135 string if no `@{push}` ref is configured. 136 137HEAD:: 138 '*' if HEAD matches current ref (the checked out branch), ' ' 139 otherwise. 140 141color:: 142 Change output color. Followed by `:<colorname>`, where names 143 are described in `color.branch.*`. 144 145align:: 146 Left-, middle-, or right-align the content between 147 %(align:...) and %(end). The "align:" is followed by 148 `width=<width>` and `position=<position>` in any order 149 separated by a comma, where the `<position>` is either left, 150 right or middle, default being left and `<width>` is the total 151 length of the content with alignment. For brevity, the 152 "width=" and/or "position=" prefixes may be omitted, and bare 153 <width> and <position> used instead. For instance, 154 `%(align:<width>,<position>)`. If the contents length is more 155 than the width then no alignment is performed. If used with 156 `--quote` everything in between %(align:...) and %(end) is 157 quoted, but if nested then only the topmost level performs 158 quoting. 159 160if:: 161 Used as %(if)...%(then)...%(end) or 162 %(if)...%(then)...%(else)...%(end). If there is an atom with 163 value or string literal after the %(if) then everything after 164 the %(then) is printed, else if the %(else) atom is used, then 165 everything after %(else) is printed. We ignore space when 166 evaluating the string before %(then), this is useful when we 167 use the %(HEAD) atom which prints either "*" or " " and we 168 want to apply the 'if' condition only on the 'HEAD' ref. 169 Append ":equals=<string>" or ":notequals=<string>" to compare 170 the value between the %(if:...) and %(then) atoms with the 171 given string. 172 173symref:: 174 The ref which the given symbolic ref refers to. If not a 175 symbolic ref, nothing is printed. Respects the `:short` and 176 `:strip` options in the same way as `refname` above. 177 178In addition to the above, for commit and tag objects, the header 179field names (`tree`, `parent`, `object`, `type`, and `tag`) can 180be used to specify the value in the header field. 181 182For commit and tag objects, the special `creatordate` and `creator` 183fields will correspond to the appropriate date or name-email-date tuple 184from the `committer` or `tagger` fields depending on the object type. 185These are intended for working on a mix of annotated and lightweight tags. 186 187Fields that have name-email-date tuple as its value (`author`, 188`committer`, and `tagger`) can be suffixed with `name`, `email`, 189and `date` to extract the named component. 190 191The complete message in a commit and tag object is `contents`. 192Its first line is `contents:subject`, where subject is the concatenation 193of all lines of the commit message up to the first blank line. The next 194line is 'contents:body', where body is all of the lines after the first 195blank line. The optional GPG signature is `contents:signature`. The 196first `N` lines of the message is obtained using `contents:lines=N`. 197Additionally, the trailers as interpreted by linkgit:git-interpret-trailers[1] 198are obtained as 'contents:trailers'. 199 200For sorting purposes, fields with numeric values sort in numeric order 201(`objectsize`, `authordate`, `committerdate`, `creatordate`, `taggerdate`). 202All other fields are used to sort in their byte-value order. 203 204There is also an option to sort by versions, this can be done by using 205the fieldname `version:refname` or its alias `v:refname`. 206 207In any case, a field name that refers to a field inapplicable to 208the object referred by the ref does not cause an error. It 209returns an empty string instead. 210 211As a special case for the date-type fields, you may specify a format for 212the date by adding `:` followed by date format name (see the 213values the `--date` option to linkgit:git-rev-list[1] takes). 214 215Some atoms like %(align) and %(if) always require a matching %(end). 216We call them "opening atoms" and sometimes denote them as %($open). 217 218When a scripting language specific quoting is in effect, everything 219between a top-level opening atom and its matching %(end) is evaluated 220according to the semantics of the opening atom and only its result 221from the top-level is quoted. 222 223 224EXAMPLES 225-------- 226 227An example directly producing formatted text. Show the most recent 2283 tagged commits: 229 230------------ 231#!/bin/sh 232 233git for-each-ref --count=3 --sort='-*authordate' \ 234--format='From: %(*authorname) %(*authoremail) 235Subject: %(*subject) 236Date: %(*authordate) 237Ref: %(*refname) 238 239%(*body) 240' 'refs/tags' 241------------ 242 243 244A simple example showing the use of shell eval on the output, 245demonstrating the use of --shell. List the prefixes of all heads: 246------------ 247#!/bin/sh 248 249git for-each-ref --shell --format="ref=%(refname)" refs/heads | \ 250while read entry 251do 252 eval "$entry" 253 echo `dirname $ref` 254done 255------------ 256 257 258A bit more elaborate report on tags, demonstrating that the format 259may be an entire script: 260------------ 261#!/bin/sh 262 263fmt=' 264 r=%(refname) 265 t=%(*objecttype) 266 T=${r#refs/tags/} 267 268 o=%(*objectname) 269 n=%(*authorname) 270 e=%(*authoremail) 271 s=%(*subject) 272 d=%(*authordate) 273 b=%(*body) 274 275 kind=Tag 276 if test "z$t" = z 277 then 278 # could be a lightweight tag 279 t=%(objecttype) 280 kind="Lightweight tag" 281 o=%(objectname) 282 n=%(authorname) 283 e=%(authoremail) 284 s=%(subject) 285 d=%(authordate) 286 b=%(body) 287 fi 288 echo "$kind $T points at a $t object $o" 289 if test "z$t" = zcommit 290 then 291 echo "The commit was authored by $n $e 292at $d, and titled 293 294 $s 295 296Its message reads as: 297" 298 echo "$b" | sed -e "s/^/ /" 299 echo 300 fi 301' 302 303eval=`git for-each-ref --shell --format="$fmt" \ 304 --sort='*objecttype' \ 305 --sort=-taggerdate \ 306 refs/tags` 307eval "$eval" 308------------ 309 310 311An example to show the usage of %(if)...%(then)...%(else)...%(end). 312This prefixes the current branch with a star. 313 314------------ 315git for-each-ref --format="%(if)%(HEAD)%(then)* %(else) %(end)%(refname:short)" refs/heads/ 316------------ 317 318 319An example to show the usage of %(if)...%(then)...%(end). 320This prints the authorname, if present. 321 322------------ 323git for-each-ref --format="%(refname)%(if)%(authorname)%(then) Authored by: %(authorname)%(end)" 324------------ 325 326SEE ALSO 327-------- 328linkgit:git-show-ref[1] 329 330GIT 331--- 332Part of the linkgit:git[1] suite