6 git-rev-parse - Pick out and massage parameters
12 'git rev-parse' [ --option ] <args>...
17 Many Git porcelainish commands take mixture of flags
18 (i.e. parameters that begin with a dash '-') and parameters
19 meant for the underlying 'git rev-list' command they use internally
20 and flags and parameters for the other commands they use
21 downstream of 'git rev-list'. This command is used to
22 distinguish between them.
31 Each of these options must appear first on the command line.
34 Use 'git rev-parse' in option parsing mode (see PARSEOPT section below).
37 Use 'git rev-parse' in shell quoting mode (see SQ-QUOTE
38 section below). In contrast to the `--sq` option below, this
39 mode does only quoting. Nothing else is done to command input.
41 Options for --parseopt
42 ~~~~~~~~~~~~~~~~~~~~~~
45 Only meaningful in `--parseopt` mode. Tells the option parser to echo
46 out the first `--` met instead of skipping it.
48 --stop-at-non-option::
49 Only meaningful in `--parseopt` mode. Lets the option parser stop at
50 the first non-option argument. This can be used to parse sub-commands
51 that take options themselves.
54 Only meaningful in `--parseopt` mode. Output the options in their
55 long form if available, and with their arguments stuck.
61 Do not output flags and parameters not meant for
62 'git rev-list' command.
65 Do not output flags and parameters meant for
66 'git rev-list' command.
69 Do not output non-flag parameters.
72 Do not output flag parameters.
78 If there is no parameter given by the user, use `<arg>`
82 Behave as if 'git rev-parse' was invoked from the `<arg>`
83 subdirectory of the working tree. Any relative filenames are
84 resolved as if they are prefixed by `<arg>` and will be printed
87 This can be used to convert arguments to a command run in a subdirectory
88 so that they can still be used after moving to the top-level of the
89 repository. For example:
92 prefix=$(git rev-parse --show-prefix)
93 cd "$(git rev-parse --show-toplevel)"
94 eval "set -- $(git rev-parse --sq --prefix "$prefix" "$@")"
98 Verify that exactly one parameter is provided, and that it
99 can be turned into a raw 20-byte SHA-1 that can be used to
100 access the object database. If so, emit it to the standard
101 output; otherwise, error out.
103 If you want to make sure that the output actually names an object in
104 your object database and/or can be used as a specific type of object
105 you require, you can add "^{type}" peeling operator to the parameter.
106 For example, `git rev-parse "$VAR^{commit}"` will make sure `$VAR`
107 names an existing object that is a commit-ish (i.e. a commit, or an
108 annotated tag that points at a commit). To make sure that `$VAR`
109 names an existing object of any type, `git rev-parse "$VAR^{object}"`
114 Only meaningful in `--verify` mode. Do not output an error
115 message if the first argument is not a valid object name;
116 instead exit with non-zero status silently.
119 Usually the output is made one line per flag and
120 parameter. This option makes output a single line,
121 properly quoted for consumption by shell. Useful when
122 you expect your parameter to contain whitespaces and
123 newlines (e.g. when using pickaxe `-S` with
124 'git diff-{asterisk}'). In contrast to the `--sq-quote` option,
125 the command input is still interpreted as usual.
128 When showing object names, prefix them with '{caret}' and
129 strip '{caret}' prefix from the object names that already have
132 --abbrev-ref[=(strict|loose)]::
133 A non-ambiguous short name of the objects name.
134 The option core.warnAmbiguousRefs is used to select the strict
139 Instead of outputting the full SHA-1 values of object names try to
140 abbreviate them to a shorter unique name. When no length is specified
141 7 is used. The minimum length is 4.
144 Usually the object names are output in SHA-1 form (with
145 possible '{caret}' prefix); this option makes them output in a
146 form as close to the original input as possible.
148 --symbolic-full-name::
149 This is similar to \--symbolic, but it omits input that
150 are not refs (i.e. branch or tag names; or more
151 explicitly disambiguating "heads/master" form, when you
152 want to name the "master" branch when there is an
153 unfortunately named tag "master"), and show them as full
154 refnames (e.g. "refs/heads/master").
160 Show all refs found in `refs/`.
162 --branches[=pattern]::
164 --remotes[=pattern]::
165 Show all branches, tags, or remote-tracking branches,
166 respectively (i.e., refs found in `refs/heads`,
167 `refs/tags`, or `refs/remotes`, respectively).
169 If a `pattern` is given, only refs matching the given shell glob are
170 shown. If the pattern does not contain a globbing character (`?`,
171 `*`, or `[`), it is turned into a prefix match by appending `/*`.
174 Show all refs matching the shell glob pattern `pattern`. If
175 the pattern does not start with `refs/`, this is automatically
176 prepended. If the pattern does not contain a globbing
177 character (`?`, `*`, or `[`), it is turned into a prefix
178 match by appending `/*`.
180 --disambiguate=<prefix>::
181 Show every object whose name begins with the given prefix.
182 The <prefix> must be at least 4 hexadecimal digits long to
183 avoid listing each and every object in the repository by
190 List the GIT_* environment variables that are local to the
191 repository (e.g. GIT_DIR or GIT_WORK_TREE, but not GIT_EDITOR).
192 Only the names of the variables are listed, not their value,
193 even if they are set.
196 Show `$GIT_DIR` if defined. Otherwise show the path to
197 the .git directory. The path shown, when relative, is
198 relative to the current working directory.
200 If `$GIT_DIR` is not defined and the current directory
201 is not detected to lie in a Git repository or work tree
202 print a message to stderr and exit with nonzero status.
204 --is-inside-git-dir::
205 When the current working directory is below the repository
206 directory print "true", otherwise "false".
208 --is-inside-work-tree::
209 When the current working directory is inside the work tree of the
210 repository print "true", otherwise "false".
212 --is-bare-repository::
213 When the repository is bare print "true", otherwise "false".
215 --resolve-git-dir <path>::
216 Check if <path> is a valid repository or a gitfile that
217 points at a valid repository, and print the location of the
218 repository. If <path> is a gitfile then the resolved path
219 to the real repository is printed.
222 When the command is invoked from a subdirectory, show the
223 path of the top-level directory relative to the current
224 directory (typically a sequence of "../", or an empty string).
227 When the command is invoked from a subdirectory, show the
228 path of the current directory relative to the top-level
232 Show the absolute path of the top-level directory.
239 Parse the date string, and output the corresponding
240 --max-age= parameter for 'git rev-list'.
243 --before=datestring::
244 Parse the date string, and output the corresponding
245 --min-age= parameter for 'git rev-list'.
248 Flags and parameters to be parsed.
251 include::revisions.txt[]
256 In `--parseopt` mode, 'git rev-parse' helps massaging options to bring to shell
257 scripts the same facilities C builtins have. It works as an option normalizer
258 (e.g. splits single switches aggregate values), a bit like `getopt(1)` does.
260 It takes on the standard input the specification of the options to parse and
261 understand, and echoes on the standard output a string suitable for `sh(1)` `eval`
262 to replace the arguments with normalized ones. In case of error, it outputs
263 usage on the standard error stream, and exits with code 129.
265 Note: Make sure you quote the result when passing it to `eval`. See
266 below for an example.
271 'git rev-parse --parseopt' input format is fully text based. It has two parts,
272 separated by a line that contains only `--`. The lines before the separator
273 (should be more than one) are used for the usage.
274 The lines after the separator describe the options.
276 Each line of options has this format:
279 <opt_spec><flags>* SP+ help LF
283 its format is the short option character, then the long option name
284 separated by a comma. Both parts are not required, though at least one
285 is necessary. `h,help`, `dry-run` and `f` are all three correct
289 `<flags>` are of `*`, `=`, `?` or `!`.
290 * Use `=` if the option takes an argument.
292 * Use `?` to mean that the option takes an optional argument. You
293 probably want to use the `--stuck-long` mode to be able to
294 unambiguously parse the optional argument.
296 * Use `*` to mean that this option should not be listed in the usage
297 generated for the `-h` argument. It's shown for `--help-all` as
298 documented in linkgit:gitcli[7].
300 * Use `!` to not make the corresponding negated long option available.
302 The remainder of the line, after stripping the spaces, is used
303 as the help associated to the option.
305 Blank lines are ignored, and lines that don't match this specification are used
306 as option group headers (start the line with a space to create such
314 some-command [options] <args>...
316 some-command does foo and bar!
320 foo some nifty option --foo
321 bar= some cool option --bar with an argument
323 An option group Header
324 C? option C with an optional argument"
326 eval "$(echo "$OPTS_SPEC" | git rev-parse --parseopt -- "$@" || echo exit $?)"
332 In `--sq-quote` mode, 'git rev-parse' echoes on the standard output a
333 single line suitable for `sh(1)` `eval`. This line is made by
334 normalizing the arguments following `--sq-quote`. Nothing other than
335 quoting the arguments is done.
337 If you want command input to still be interpreted as usual by
338 'git rev-parse' before the output is shell quoted, see the `--sq`
345 $ cat >your-git-script.sh <<\EOF
347 args=$(git rev-parse --sq-quote "$@") # quote user-supplied arguments
348 command="git frotz -n24 $args" # and use it inside a handcrafted
353 $ sh your-git-script.sh "a b'c"
359 * Print the object name of the current commit:
362 $ git rev-parse --verify HEAD
365 * Print the commit object name from the revision in the $REV shell variable:
368 $ git rev-parse --verify $REV^{commit}
371 This will error out if $REV is empty or not a valid revision.
376 $ git rev-parse --default master --verify $REV
379 but if $REV is empty, the commit object name from master will be printed.
383 Part of the linkgit:git[1] suite