git-show-branch(1)

—

NAME

git-show-branch - Show branches and their commits

SYNOPSIS

bash

git show-branch\n [-a | --all] [-r | --remotes] [--topo-order | --date-order]
\n
                [--current] [--color[=<when>] | --no-color] [--sparse]
\n
                [--more=<n> | --list | --independent | --merge-base]
\n
                [--no-name | --sha1-name] [--topics]
\n
                [(<rev> | <glob>)...]
\ngit show-branch\n (-g | --reflog)[=<n>[,<base>]] [--list] [<ref>]

DESCRIPTION

Shows the commit ancestry graph starting from the commits named with <rev>s or <glob>s (or all refs under refs/heads and/or refs/tags) semi-visually.

It cannot show more than 26 branches and commits at a time.

It uses showbranch.default multi-valued configuration items if no <rev> or <glob> is given on the command line.

OPTIONS

<rev>

<glob>

-r, --remotes

-a, --all

--current

--topo-order

--date-order

--sparse

--more=<n>

--list

--merge-base

--independent

--no-name

--sha1-name

--topics

-g, --reflog[=<n>[,<base>]] [<ref>]

--color[=<when>]

--no-color

Note that --more, --list, --independent, and --merge-base options are mutually exclusive.

Given N <ref>s, the first N lines are the one-line description from their commit message. The branch head that is pointed at by $GIT_DIR/HEAD is prefixed with an asterisk * character while other heads are prefixed with a ! character.

Following these N lines, a one-line log for each commit is displayed, indented N places. If a commit is on the I-th branch, the I-th indentation character shows a + sign; otherwise it shows a space. Merge commits are denoted by a - sign. Each commit shows a short name that can be used as an extended SHA-1 to name that commit.

The following example shows three branches, "master", "fixes", and "mhf":

bash

$ git show-branch master fixes mhf
* [master] Add 'git show-branch'.
\n
 ! [fixes] Introduce "reset type" flag to "git reset"
\n
  ! [mhf] Allow "+remote:local" refspec to cause --force when fetching.
---
\n
  + [mhf] Allow "+remote:local" refspec to cause --force when fetching.
\n
  + [mhf~1] Use git-octopus when pulling more than one head.
\n
 +  [fixes] Introduce "reset type" flag to "git reset"
\n
  + [mhf~2] "git fetch --force".
\n
  + [mhf~3] Use .git/remote/origin, not .git/branches/origin.
\n
  + [mhf~4] Make "git pull" and "git fetch" default to origin
\n
  + [mhf~5] Infamous 'octopus merge'
\n
  + [mhf~6] Retire git-parse-remote.
\n
  + [mhf~7] Multi-head fetch.
\n
  + [mhf~8] Start adding the $GIT_DIR/remotes/ support.
*++ [master] Add 'git show-branch'.

These three branches all forked from a common commit, [master], whose commit message is "Add 'git show-branch'". The "fixes" branch adds one commit "Introduce "reset type" flag to "git reset"". The "mhf" branch adds many other commits. The current branch is "master".

EXAMPLES

If you keep your primary branches immediately under refs/heads, and topic branches in subdirectories of it, having the following in the configuration file may help:

bash

[showbranch]
\n
        default = --topo-order
\n
        default = heads/*

With this, git show-branch without extra parameters would show only the primary branches. In addition, if you happen to be on your topic branch, it is shown as well.

bash

$ git show-branch --reflog="10,1 hour ago" --list master

shows 10 reflog entries going back from the tip as of 1 hour ago. Without --list, the output also shows how these tips are topologically related to each other.

CONFIGURATION

Everything below this line in this section is selectively included from the git-config(1) documentation. The content is the same as what’s found there:

showBranch.default

GIT

Part of the git(1) suite