git-branch(1) - List, create, or delete branches
-d, --delete
    Delete a branch. The branch must be fully merged in its upstream branch, or in HEAD if no upstream
    was set with --track or --set-upstream.
-D
    Delete a branch irrespective of its merged status.
-l, --create-reflog
    Create the branch’s reflog. This activates recording of all changes made to the branch ref, enabling
    use of date based sha1 expressions such as "<branchname>@{yesterday}". Note that in non-bare
    repositories, reflogs are usually enabled by default by the core.logallrefupdates config option.
-f, --force
    Reset <branchname> to <startpoint> if <branchname> exists already. Without -f git branch refuses to
    change an existing branch.
-m, --move
    Move/rename a branch and the corresponding reflog.
-M
    Move/rename a branch even if the new branch name already exists.
--color[=<when>]
    Color branches to highlight current, local, and remote-tracking branches. The value must be always
    (the default), never, or auto.
--no-color
    Turn off branch colors, even when the configuration file gives the default to color output. Same as
    --color=never.
-r, --remotes
    List or delete (if used with -d) the remote-tracking branches.
-a, --all
    List both remote-tracking branches and local branches.
--list
    Activate the list mode.  git branch <pattern> would try to create a branch, use git branch --list
    <pattern> to list matching branches.
-v, --verbose
    When in list mode, show sha1 and commit subject line for each head, along with relationship to
    upstream branch (if any). If given twice, print the name of the upstream branch, as well.
--abbrev=<length>
    Alter the sha1’s minimum display length in the output listing. The default value is 7 and can be
    overridden by the core.abbrev config option.
--no-abbrev
    Display the full sha1s in the output listing rather than abbreviating them.
-t, --track
    When creating a new branch, set up configuration to mark the start-point branch as "upstream" from
    the new branch. This configuration will tell git to show the relationship between the two branches in
    git status and git branch -v. Furthermore, it directs git pull without arguments to pull from the
    upstream when the new branch is checked out.

    This behavior is the default when the start point is a remote-tracking branch. Set the
    branch.autosetupmerge configuration variable to false if you want git checkout and git branch to
    always behave as if --no-track were given. Set it to always if you want this behavior when the
    start-point is either a local or remote-tracking branch.
--no-track
    Do not set up "upstream" configuration, even if the branch.autosetupmerge configuration variable is
    true.
--set-upstream
    If specified branch does not exist yet or if --force has been given, acts exactly like --track.
    Otherwise sets up configuration like --track would when creating the branch, except that where branch
    points to is not changed.
--edit-description
    Open an editor and edit the text to explain what the branch is for, to be used by various other
    commands (e.g.  request-pull).
--contains <commit>
    Only list branches which contain the specified commit.
--merged [<commit>]
    Only list branches whose tips are reachable from the specified commit (HEAD if not specified).
--no-merged [<commit>]
    Only list branches whose tips are not reachable from the specified commit (HEAD if not specified).
<branchname>
    The name of the branch to create or delete. The new branch name must pass all checks defined by git-
    check-ref-format(1). Some of these checks may restrict the characters allowed in a branch name.

<start-point>
    The new branch head will point to this commit. It may be given as a branch name, a commit-id, or a
    tag. If this option is omitted, the current HEAD will be used instead.

<oldbranch>
    The name of an existing branch to rename.

<newbranch>
    The new name for an existing branch. The same restrictions as for <branchname> apply.