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.
57 Do not output flags and parameters not meant for
58 'git rev-list' command.
61 Do not output flags and parameters meant for
62 'git rev-list' command.
65 Do not output non-flag parameters.
68 Do not output flag parameters.
74 If there is no parameter given by the user, use `<arg>`
78 Verify that exactly one parameter is provided, and that it
79 can be turned into a raw 20-byte SHA-1 that can be used to
80 access the object database. If so, emit it to the standard
81 output; otherwise, error out.
83 If you want to make sure that the output actually names an object in
84 your object database and/or can be used as a specific type of object
85 you require, you can add "^{type}" peeling operator to the parmeter.
86 For example, `git rev-parse "$VAR^{commit}"` will make sure `$VAR`
87 names an existing object that is a commit-ish (i.e. a commit, or an
88 annotated tag that points at a commit). To make sure that `$VAR`
89 names an existing object of any type, `git rev-parse "$VAR^{object}"`
94 Only meaningful in `--verify` mode. Do not output an error
95 message if the first argument is not a valid object name;
96 instead exit with non-zero status silently.
99 Usually the output is made one line per flag and
100 parameter. This option makes output a single line,
101 properly quoted for consumption by shell. Useful when
102 you expect your parameter to contain whitespaces and
103 newlines (e.g. when using pickaxe `-S` with
104 'git diff-{asterisk}'). In contrast to the `--sq-quote` option,
105 the command input is still interpreted as usual.
108 When showing object names, prefix them with '{caret}' and
109 strip '{caret}' prefix from the object names that already have
112 --abbrev-ref[=(strict|loose)]::
113 A non-ambiguous short name of the objects name.
114 The option core.warnAmbiguousRefs is used to select the strict
119 Instead of outputting the full SHA-1 values of object names try to
120 abbreviate them to a shorter unique name. When no length is specified
121 7 is used. The minimum length is 4.
124 Usually the object names are output in SHA-1 form (with
125 possible '{caret}' prefix); this option makes them output in a
126 form as close to the original input as possible.
128 --symbolic-full-name::
129 This is similar to \--symbolic, but it omits input that
130 are not refs (i.e. branch or tag names; or more
131 explicitly disambiguating "heads/master" form, when you
132 want to name the "master" branch when there is an
133 unfortunately named tag "master"), and show them as full
134 refnames (e.g. "refs/heads/master").
140 Show all refs found in `refs/`.
142 --branches[=pattern]::
144 --remotes[=pattern]::
145 Show all branches, tags, or remote-tracking branches,
146 respectively (i.e., refs found in `refs/heads`,
147 `refs/tags`, or `refs/remotes`, respectively).
149 If a `pattern` is given, only refs matching the given shell glob are
150 shown. If the pattern does not contain a globbing character (`?`,
151 `*`, or `[`), it is turned into a prefix match by appending `/*`.
154 Show all refs matching the shell glob pattern `pattern`. If
155 the pattern does not start with `refs/`, this is automatically
156 prepended. If the pattern does not contain a globbing
157 character (`?`, `*`, or `[`), it is turned into a prefix
158 match by appending `/*`.
160 --disambiguate=<prefix>::
161 Show every object whose name begins with the given prefix.
162 The <prefix> must be at least 4 hexadecimal digits long to
163 avoid listing each and every object in the repository by
170 List the GIT_* environment variables that are local to the
171 repository (e.g. GIT_DIR or GIT_WORK_TREE, but not GIT_EDITOR).
172 Only the names of the variables are listed, not their value,
173 even if they are set.
176 Show `$GIT_DIR` if defined. Otherwise show the path to
177 the .git directory. The path shown, when relative, is
178 relative to the current working directory.
180 If `$GIT_DIR` is not defined and the current directory
181 is not detected to lie in a Git repository or work tree
182 print a message to stderr and exit with nonzero status.
184 --is-inside-git-dir::
185 When the current working directory is below the repository
186 directory print "true", otherwise "false".
188 --is-inside-work-tree::
189 When the current working directory is inside the work tree of the
190 repository print "true", otherwise "false".
192 --is-bare-repository::
193 When the repository is bare print "true", otherwise "false".
195 --resolve-git-dir <path>::
196 Check if <path> is a valid repository or a gitfile that
197 points at a valid repository, and print the location of the
198 repository. If <path> is a gitfile then the resolved path
199 to the real repository is printed.
202 When the command is invoked from a subdirectory, show the
203 path of the top-level directory relative to the current
204 directory (typically a sequence of "../", or an empty string).
207 When the command is invoked from a subdirectory, show the
208 path of the current directory relative to the top-level
212 Show the absolute path of the top-level directory.
219 Parse the date string, and output the corresponding
220 --max-age= parameter for 'git rev-list'.
223 --before=datestring::
224 Parse the date string, and output the corresponding
225 --min-age= parameter for 'git rev-list'.
228 Flags and parameters to be parsed.
231 include::revisions.txt[]
236 In `--parseopt` mode, 'git rev-parse' helps massaging options to bring to shell
237 scripts the same facilities C builtins have. It works as an option normalizer
238 (e.g. splits single switches aggregate values), a bit like `getopt(1)` does.
240 It takes on the standard input the specification of the options to parse and
241 understand, and echoes on the standard output a string suitable for `sh(1)` `eval`
242 to replace the arguments with normalized ones. In case of error, it outputs
243 usage on the standard error stream, and exits with code 129.
245 Note: Make sure you quote the result when passing it to `eval`. See
246 below for an example.
251 'git rev-parse --parseopt' input format is fully text based. It has two parts,
252 separated by a line that contains only `--`. The lines before the separator
253 (should be more than one) are used for the usage.
254 The lines after the separator describe the options.
256 Each line of options has this format:
259 <opt_spec><flags>* SP+ help LF
263 its format is the short option character, then the long option name
264 separated by a comma. Both parts are not required, though at least one
265 is necessary. `h,help`, `dry-run` and `f` are all three correct
269 `<flags>` are of `*`, `=`, `?` or `!`.
270 * Use `=` if the option takes an argument.
272 * Use `?` to mean that the option is optional (though its use is discouraged).
274 * Use `*` to mean that this option should not be listed in the usage
275 generated for the `-h` argument. It's shown for `--help-all` as
276 documented in linkgit:gitcli[7].
278 * Use `!` to not make the corresponding negated long option available.
280 The remainder of the line, after stripping the spaces, is used
281 as the help associated to the option.
283 Blank lines are ignored, and lines that don't match this specification are used
284 as option group headers (start the line with a space to create such
292 some-command [options] <args>...
294 some-command does foo and bar!
298 foo some nifty option --foo
299 bar= some cool option --bar with an argument
301 An option group Header
302 C? option C with an optional argument"
304 eval "$(echo "$OPTS_SPEC" | git rev-parse --parseopt -- "$@" || echo exit $?)"
310 In `--sq-quote` mode, 'git rev-parse' echoes on the standard output a
311 single line suitable for `sh(1)` `eval`. This line is made by
312 normalizing the arguments following `--sq-quote`. Nothing other than
313 quoting the arguments is done.
315 If you want command input to still be interpreted as usual by
316 'git rev-parse' before the output is shell quoted, see the `--sq`
323 $ cat >your-git-script.sh <<\EOF
325 args=$(git rev-parse --sq-quote "$@") # quote user-supplied arguments
326 command="git frotz -n24 $args" # and use it inside a handcrafted
331 $ sh your-git-script.sh "a b'c"
337 * Print the object name of the current commit:
340 $ git rev-parse --verify HEAD
343 * Print the commit object name from the revision in the $REV shell variable:
346 $ git rev-parse --verify $REV^{commit}
349 This will error out if $REV is empty or not a valid revision.
354 $ git rev-parse --default master --verify $REV
357 but if $REV is empty, the commit object name from master will be printed.
361 Part of the linkgit:git[1] suite