Synopsis

git rev-parse [<options>] <arg>...

Description

The git rev-parse command resolves Git references and arguments. It turns symbolic names (branches, tags, HEAD~3, HEAD@{yesterday}) into 40-character SHAs, normalizes options, and answers introspection questions about the current repository (top-level path, Git directory, whether we're in a worktree). It is the Swiss Army knife of Git scripting.

In day-to-day use, git rev-parse integrates closely with shell aliases, editor plugins, and continuous integration. Power users often add aliases that combine flags they always pass, or wrap the command in scripts that enforce team conventions. Output formatting can be customized via Git config — pretty formats, color schemes, and pager behavior are all tunable. When something goes wrong, the first diagnostic step is usually to re-run the command with GIT_TRACE=1 in the environment, which reveals the underlying plumbing calls. For unusual situations, the --help output (git rev-parse --help) opens the full manual page with details on every option, including those rarely used in casual workflows but essential for debugging or scripting at scale.

Understanding how git rev-parse interacts with the rest of Git's data model — the object database, the index, refs, and the working tree — pays dividends. Each command operates on some subset of these pieces, and knowing which it touches helps predict outcomes and recover from mistakes. Reading the official Git documentation alongside hands-on practice in a throwaway repository is the fastest way to internalize the nuances. Most production issues with Git stem from one of three causes: surprising default behavior, partial network operations, or rewriting history that was already shared. A working mental model of git rev-parse's side effects helps avoid all three.

When to Use

You'll see git rev-parse in nearly every shell script that wraps Git: to get the current branch name, the repo root, or to validate that an argument is a valid commit. Most users don't run it directly day-to-day, but knowledge of it dramatically improves Git scripting fluency.

Common Options

Examples

git rev-parse HEAD
# Full SHA of current commit

git rev-parse --abbrev-ref HEAD
# Current branch name (or "HEAD" if detached)

git rev-parse --show-toplevel
# Path to repo root, useful in scripts

git rev-parse --verify origin/main >/dev/null && echo OK
# Test whether a ref exists

Common Mistakes

Using git rev-parse on user input without --verify can succeed for ambiguous arguments and produce surprising results. In subshells, --show-toplevel is a more reliable anchor than $PWD.

Related Commands

git symbolic-ref, git rev-list, git for-each-ref, git config