Git branch 命令

更新时间: 2019-07-13 17:17

git-branch - List, create, or delete branches

语法

git branch [--color[=<when>] | --no-color] [-r | -a]
        [--list] [-v [--abbrev=<length> | --no-abbrev]]
        [--column[=<options>] | --no-column] [--sort=<key>]
        [(--merged | --no-merged) [<commit>]]
        [--contains [<commit]] [--no-contains [<commit>]]
        [--points-at <object>] [--format=<format>] [<pattern>...]
git branch [--set-upstream | --track | --no-track] [-l] [-f] <branchname> [<start-point>]
git branch (--set-upstream-to=<upstream> | -u <upstream>) [<branchname>]
git branch --unset-upstream [<branchname>]
git branch (-m | -M) [<oldbranch>] <newbranch>
git branch (-c | -C) [<oldbranch>] <newbranch>
git branch (-d | -D) [-r] <branchname>...
git branch --edit-description [<branchname>]

参数

-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
        Shortcut for --delete --force.

-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. The negated form --no-create-reflog only overrides an earlier --create-reflog, but currently
        does not negate the setting of core.logAllRefUpdates.

-f, --force
        Reset <branchname> to <startpoint>, even if <branchname> exists already. Without -f, git branch refuses to change an existing
        branch. In combination with -d (or --delete), allow deleting the branch irrespective of its merged status. In combination with -m
        (or --move), allow renaming the branch even if the new branch name already exists, the same applies for -c (or --copy).

-m, --move
        Move/rename a branch and the corresponding reflog.

-M
        Shortcut for --move --force.

-c, --copy
        Copy a branch and the corresponding reflog.

-C
        Shortcut for --copy --force.

--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.

-i, --ignore-case
        Sorting and filtering branches are case insensitive.

--column[=<options>], --no-column
        Display branch listing in columns. See configuration variable column.branch for option syntax.--column and --no-column without
        options are equivalent to always and never respectively.

        This option is only applicable in non-verbose mode.

-r, --remotes
        List or delete (if used with -d) the remote-tracking branches.

-a, --all
        List both remote-tracking branches and local branches.

--list
        List branches. With optional <pattern>..., e.g.  git branch --list 'maint-*', list only the branches that match the pattern(s).

        This should not be confused with git branch -l <branchname>, which creates a branch named <branchname> with a reflog. See
        --create-reflog above for details.

-v, -vv, --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 (see also git remote show <remote>).

-q, --quiet
        Be more quiet when creating or deleting a branch, suppressing non-error messages.

--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 branch.<name>.remote and branch.<name>.merge configuration entries 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
        As this option had confusing syntax, it is no longer supported. Please use --track or --set-upstream-to instead.

-u <upstream>, --set-upstream-to=<upstream>
        Set up <branchname>'s tracking information so <upstream> is considered <branchname>'s upstream branch. If no <branchname> is
        specified, then it defaults to the current branch.

--unset-upstream
        Remove the upstream information for <branchname>. If no branch is specified it defaults to the current branch.

--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.  format-patch,
        request-pull, and merge (if enabled)). Multi-line explanations may be used.

--contains [<commit>]
        Only list branches which contain the specified commit (HEAD if not specified). Implies --list.

--no-contains [<commit>]
        Only list branches which don't contain the specified commit (HEAD if not specified). Implies --list.

--merged [<commit>]
        Only list branches whose tips are reachable from the specified commit (HEAD if not specified). Implies --list, incompatible with
        --no-merged.

--no-merged [<commit>]
        Only list branches whose tips are not reachable from the specified commit (HEAD if not specified). Implies --list, incompatible
        with --merged.

<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.

--sort=<key>
<oldbranch>
        The name of an existing branch to rename.

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

--sort=<key>
        Sort based on the key given. Prefix - to sort in descending order of the value. You may use the --sort=<key> option multiple times,
        in which case the last key becomes the primary key. The keys supported are the same as those in git for-each-ref. Sort order
        defaults to sorting based on the full refname (including refs/...  prefix). This lists detached HEAD (if present) first, then local
        branches and finally remote-tracking branches.

--points-at <object>
        Only list branches of the given object.

--format <format>
        A string that interpolates %(fieldname) from a branch ref being shown and the object it points at. The format is the same as that
        of git-for-each-ref(1).

使用示例

# 列出所有本地分支
$ git branch

# 列出所有远程分支
$ git branch -r

# 列出所有本地分支和远程分支
$ git branch -a

# 新建一个分支,但依然停留在当前分支
$ git branch [branch-name]

查看更多 git branch 命令的使用方法,可以使用命令:

git help branch
Using Google App Engine

Using Google App Engine

Charles Severance / O'Reilly Media / 2009-5-23 / USD 29.99

With this book, you can build exciting, scalable web applications quickly and confidently, using Google App Engine - even if you have little or no experience in programming or web development. App Eng......一起来看看 《Using Google App Engine》 这本书的介绍吧!

JS 压缩/解压工具

JS 压缩/解压工具

在线压缩/解压 JS 代码

XML 在线格式化

XML 在线格式化

在线 XML 格式化压缩工具

HSV CMYK 转换工具

HSV CMYK 转换工具

HSV CMYK互换工具