IT系/リファレンス/Gitコマンド/git_branch

git branch

ブランチを操作するコマンド。
ブランチの確認、編集、作成、削除など。

用例

ローカルブランチの一覧を表示
```
git branch
```
リモートブランチの一覧を表示
```
git branch -r
```
ローカルブランチとリモートブランチの両方を一覧表示
```
git branch -a
```
ブランチ「hoge」を作成
```
git branch hoge
```
ブランチ「hoge」を削除
```
git branch -d hoge
```
ブランチ「hoge」を強制的に削除
```
git branch -D hoge
```
ブランチの名称を「fuga」に変更
```
git branch -m fuga
```
ブランチ「hoge」の名称を「fuga」に変更
```
git branch -m hoge fuga
```
ブランチ毎の最新コミットIDとメッセージを表示
```
git branch -v
```
ローカルブランチと追跡ブランチの対応一覧を表示
```
git branch -vv
```
HEADにマージ済みのブランチの一覧を表示
```
git branch --merged
```
HEADにマージされていないブランチの一覧を表示
```
git branch --no-merged
```
現在チェックアウトしているブランチが、<upstream>で指定したリモートブランチを追跡するようにする
```
git branch -u <upstream>
```
現在チェックアウトしているブランチが追跡しているリモートブランチとの紐付きを解除する
```
git branch --unset-upstream
```

書式

git branch [options] [value]

公式によると以下の通り。

git branch [--color[=<when>] | --no-color] [--show-current]
           [-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>]
           [(-r | --remotes) | (-a | --all)]
           [--list] [<pattern>…]
git branch [--track | --no-track] [-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>…&#8203;
git branch --edit-description [<branchname>]

options

--color	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.
--show-current	Print the name of the current branch. In detached HEAD state, nothing is printed.
-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>).
--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.
--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.
--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 the value configured for the branch.sort variable if exists, or 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. See git-config.
--merged	Only list branches whose tips are reachable from the specified commit (HEAD if not specified). Implies --list, incompatible with --no-merged.
--no-merged	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. 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.
--contains	Only list branches which contain the specified commit (HEAD if not specified). Implies --list.
--no-contains	Only list branches which don’t contain the specified commit (HEAD if not specified). Implies --list.
--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.
-r \| --remotes	リモートブランチの一覧を表示。-dと共に使用する場合は削除。
-a \| --all	ローカルブランチとリモートブランチ（追跡ブランチ）の両方を一覧表示
-l \| --list	List branches. With optional <pattern>..., e.g. git branch --list 'maint-*', list only the branches that match the pattern(s).
-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.
-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).
--set-upstream	As this option had confusing syntax, it is no longer supported. Please use --track or --set-upstream-to instead.
--set-upstream-to=<upstream> \| -u <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.
-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.
-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-to.
-D	Shortcut for --delete --force.
--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.
--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.
-i \| --ignore-case	Sorting and filtering branches are case insensitive.
-q \| --quiet	Be more quiet when creating or deleting a branch, suppressing non-error messages.