]>
Commit | Line | Data |
---|---|---|
215a7ad1 JH |
1 | git-branch(1) |
2 | ============= | |
7fc9d69f JH |
3 | |
4 | NAME | |
5 | ---- | |
c3f0baac | 6 | git-branch - List, create, or delete branches |
7fc9d69f JH |
7 | |
8 | SYNOPSIS | |
9 | -------- | |
dd181119 | 10 | [verse] |
73e9da01 | 11 | 'git branch' [--color[=<when>] | --no-color] [-r | -a] |
cddd127b | 12 | [--list] [-v [--abbrev=<length> | --no-abbrev]] |
d8d33736 | 13 | [(--merged | --no-merged | --contains) [<commit>]] [<pattern>...] |
4fc50066 | 14 | 'git branch' [--set-upstream | --track | --no-track] [-l] [-f] <branchname> [<start-point>] |
b1889c36 JN |
15 | 'git branch' (-m | -M) [<oldbranch>] <newbranch> |
16 | 'git branch' (-d | -D) [-r] <branchname>... | |
7fc9d69f JH |
17 | |
18 | DESCRIPTION | |
19 | ----------- | |
049716b3 | 20 | |
e5ac1217 | 21 | With no arguments, existing branches are listed and the current branch will |
049716b3 | 22 | be highlighted with an asterisk. Option `-r` causes the remote-tracking |
cddd127b MG |
23 | branches to be listed, and option `-a` shows both. This list mode is also |
24 | activated by the `--list` and `-v` options (see below). | |
d8d33736 MG |
25 | <pattern> restricts the output to matching branches, the pattern is a shell |
26 | wildcard (i.e., matched using fnmatch(3)) | |
27 | Multiple patterns may be given; if any of them matches, the tag is shown. | |
049716b3 | 28 | |
e5ac1217 DM |
29 | With `--contains`, shows only the branches that contain the named commit |
30 | (in other words, the branches whose tip commits are descendants of the | |
049716b3 JH |
31 | named commit). With `--merged`, only branches merged into the named |
32 | commit (i.e. the branches whose tip commits are reachable from the named | |
33 | commit) will be listed. With `--no-merged` only branches not merged into | |
e5ac1217 DM |
34 | the named commit will be listed. If the <commit> argument is missing it |
35 | defaults to 'HEAD' (i.e. the tip of the current branch). | |
7fc9d69f | 36 | |
bb35f35e JN |
37 | The command's second form creates a new branch head named <branchname> |
38 | which points to the current 'HEAD', or <start-point> if given. | |
2eaf273d | 39 | |
46749204 FMQ |
40 | Note that this will create the new branch, but it will not switch the |
41 | working tree to it; use "git checkout <newbranch>" to switch to the | |
42 | new branch. | |
43 | ||
29b9a66f | 44 | When a local branch is started off a remote-tracking branch, git sets up the |
0b444cdb | 45 | branch so that 'git pull' will appropriately merge from |
29b9a66f | 46 | the remote-tracking branch. This behavior may be changed via the global |
572fc81d | 47 | `branch.autosetupmerge` configuration flag. That setting can be |
4eec6f98 MM |
48 | overridden by using the `--track` and `--no-track` options, and |
49 | changed later using `git branch --set-upstream`. | |
0746d19a | 50 | |
c976d415 LH |
51 | With a '-m' or '-M' option, <oldbranch> will be renamed to <newbranch>. |
52 | If <oldbranch> had a corresponding reflog, it is renamed to match | |
53 | <newbranch>, and a reflog entry is created to remember the branch | |
54 | renaming. If <newbranch> exists, -M must be used to force the rename | |
55 | to happen. | |
56 | ||
2eaf273d | 57 | With a `-d` or `-D` option, `<branchname>` will be deleted. You may |
3a4b3f26 | 58 | specify more than one branch for deletion. If the branch currently |
1e72a40d JH |
59 | has a reflog then the reflog will also be deleted. |
60 | ||
61 | Use -r together with -d to delete remote-tracking branches. Note, that it | |
62 | only makes sense to delete remote-tracking branches if they no longer exist | |
0b444cdb | 63 | in the remote repository or if 'git fetch' was configured not to fetch |
e5ac1217 DM |
64 | them again. See also the 'prune' subcommand of linkgit:git-remote[1] for a |
65 | way to clean up all obsolete remote-tracking branches. | |
dd181119 JL |
66 | |
67 | ||
7fc9d69f JH |
68 | OPTIONS |
69 | ------- | |
d4072c97 | 70 | -d:: |
171edcbb | 71 | --delete:: |
fff0d0ab JN |
72 | Delete a branch. The branch must be fully merged in its |
73 | upstream branch, or in `HEAD` if no upstream was set with | |
74 | `--track` or `--set-upstream`. | |
d4072c97 AE |
75 | |
76 | -D:: | |
1e72a40d | 77 | Delete a branch irrespective of its merged status. |
d4072c97 | 78 | |
3a4b3f26 | 79 | -l:: |
171edcbb | 80 | --create-reflog:: |
792d2370 JK |
81 | Create the branch's reflog. This activates recording of |
82 | all changes made to the branch ref, enabling use of date | |
967506bb | 83 | based sha1 expressions such as "<branchname>@\{yesterday}". |
4c35f0db JK |
84 | Note that in non-bare repositories, reflogs are usually |
85 | enabled by default by the `core.logallrefupdates` config option. | |
3a4b3f26 | 86 | |
075dd8ee | 87 | -f:: |
f7aec129 | 88 | --force:: |
fcfdf797 | 89 | Reset <branchname> to <startpoint> if <branchname> exists |
0b444cdb | 90 | already. Without `-f` 'git branch' refuses to change an existing branch. |
2eaf273d | 91 | |
c976d415 | 92 | -m:: |
171edcbb | 93 | --move:: |
c976d415 LH |
94 | Move/rename a branch and the corresponding reflog. |
95 | ||
96 | -M:: | |
e5ac1217 | 97 | Move/rename a branch even if the new branch name already exists. |
c976d415 | 98 | |
73e9da01 | 99 | --color[=<when>]:: |
29b9a66f MM |
100 | Color branches to highlight current, local, and |
101 | remote-tracking branches. | |
73e9da01 | 102 | The value must be always (the default), never, or auto. |
f3673988 BG |
103 | |
104 | --no-color:: | |
105 | Turn off branch colors, even when the configuration file gives the | |
106 | default to color output. | |
73e9da01 | 107 | Same as `--color=never`. |
f3673988 | 108 | |
2eaf273d | 109 | -r:: |
171edcbb | 110 | --remotes:: |
7dda22e3 | 111 | List or delete (if used with -d) the remote-tracking branches. |
bfcc9214 AP |
112 | |
113 | -a:: | |
171edcbb | 114 | --all:: |
bfcc9214 | 115 | List both remote-tracking branches and local branches. |
075dd8ee | 116 | |
cddd127b | 117 | --list:: |
d8d33736 MG |
118 | Activate the list mode. `git branch <pattern>` would try to create a branch, |
119 | use `git branch --list <pattern>` to list matching branches. | |
cddd127b | 120 | |
3240240f SB |
121 | -v:: |
122 | --verbose:: | |
2d8a7f0b JK |
123 | Show sha1 and commit subject line for each head, along with |
124 | relationship to upstream branch (if any). If given twice, print | |
125 | the name of the upstream branch, as well. | |
cddd127b | 126 | `--list` is implied by all verbosity options. |
75e6e213 LH |
127 | |
128 | --abbrev=<length>:: | |
e5ac1217 | 129 | Alter the sha1's minimum display length in the output listing. |
b792c067 NK |
130 | The default value is 7 and can be overridden by the `core.abbrev` |
131 | config option. | |
75e6e213 | 132 | |
5e00f6fa | 133 | --no-abbrev:: |
e5ac1217 | 134 | Display the full sha1s in the output listing rather than abbreviating them. |
5e00f6fa | 135 | |
be427d75 | 136 | -t:: |
84d176ce | 137 | --track:: |
167d7445 JK |
138 | When creating a new branch, set up configuration to mark the |
139 | start-point branch as "upstream" from the new branch. This | |
140 | configuration will tell git to show the relationship between the | |
141 | two branches in `git status` and `git branch -v`. Furthermore, | |
142 | it directs `git pull` without arguments to pull from the | |
143 | upstream when the new branch is checked out. | |
144 | + | |
29b9a66f | 145 | This behavior is the default when the start point is a remote-tracking branch. |
167d7445 JK |
146 | Set the branch.autosetupmerge configuration variable to `false` if you |
147 | want `git checkout` and `git branch` to always behave as if '--no-track' | |
148 | were given. Set it to `always` if you want this behavior when the | |
29b9a66f | 149 | start-point is either a local or remote-tracking branch. |
84d176ce FMQ |
150 | |
151 | --no-track:: | |
167d7445 | 152 | Do not set up "upstream" configuration, even if the |
70e96647 | 153 | branch.autosetupmerge configuration variable is true. |
84d176ce | 154 | |
4fc50066 IL |
155 | --set-upstream:: |
156 | If specified branch does not exist yet or if '--force' has been | |
157 | given, acts exactly like '--track'. Otherwise sets up configuration | |
158 | like '--track' would when creating the branch, except that where | |
159 | branch points to is not changed. | |
160 | ||
9a7ea2b1 LH |
161 | --contains <commit>:: |
162 | Only list branches which contain the specified commit. | |
163 | ||
58d2c961 JN |
164 | --merged [<commit>]:: |
165 | Only list branches whose tips are reachable from the | |
166 | specified commit (HEAD if not specified). | |
9a7ea2b1 | 167 | |
58d2c961 JN |
168 | --no-merged [<commit>]:: |
169 | Only list branches whose tips are not reachable from the | |
170 | specified commit (HEAD if not specified). | |
9a7ea2b1 | 171 | |
52a22d1e | 172 | <branchname>:: |
d4072c97 | 173 | The name of the branch to create or delete. |
2b1f4247 | 174 | The new branch name must pass all checks defined by |
5162e697 | 175 | linkgit:git-check-ref-format[1]. Some of these checks |
2b1f4247 | 176 | may restrict the characters allowed in a branch name. |
7fc9d69f | 177 | |
075dd8ee | 178 | <start-point>:: |
bb35f35e JN |
179 | The new branch head will point to this commit. It may be |
180 | given as a branch name, a commit-id, or a tag. If this | |
181 | option is omitted, the current HEAD will be used instead. | |
2eaf273d | 182 | |
c976d415 LH |
183 | <oldbranch>:: |
184 | The name of an existing branch to rename. | |
185 | ||
186 | <newbranch>:: | |
187 | The new name for an existing branch. The same restrictions as for | |
e5ac1217 | 188 | <branchname> apply. |
7fc9d69f | 189 | |
1e2ccd3a JH |
190 | |
191 | Examples | |
2eaf273d | 192 | -------- |
1e2ccd3a | 193 | |
e5ac1217 | 194 | Start development from a known tag:: |
1e2ccd3a JH |
195 | + |
196 | ------------ | |
197 | $ git clone git://git.kernel.org/pub/scm/.../linux-2.6 my2.6 | |
198 | $ cd my2.6 | |
2eaf273d | 199 | $ git branch my2.6.14 v2.6.14 <1> |
1e2ccd3a | 200 | $ git checkout my2.6.14 |
1e2ccd3a | 201 | ------------ |
2eaf273d SE |
202 | + |
203 | <1> This step and the next one could be combined into a single step with | |
204 | "checkout -b my2.6.14 v2.6.14". | |
1e2ccd3a | 205 | |
e5ac1217 | 206 | Delete an unneeded branch:: |
1e2ccd3a JH |
207 | + |
208 | ------------ | |
209 | $ git clone git://git.kernel.org/.../git.git my.git | |
210 | $ cd my.git | |
33b1f3d5 FM |
211 | $ git branch -d -r origin/todo origin/html origin/man <1> |
212 | $ git branch -D test <2> | |
2eaf273d SE |
213 | ------------ |
214 | + | |
e5ac1217 DM |
215 | <1> Delete the remote-tracking branches "todo", "html" and "man". The next |
216 | 'fetch' or 'pull' will create them again unless you configure them not to. | |
217 | See linkgit:git-fetch[1]. | |
218 | <2> Delete the "test" branch even if the "master" branch (or whichever branch | |
219 | is currently checked out) does not have all commits from the test branch. | |
2eaf273d SE |
220 | |
221 | ||
222 | Notes | |
223 | ----- | |
224 | ||
e5ac1217 | 225 | If you are creating a branch that you want to checkout immediately, it is |
2eaf273d SE |
226 | easier to use the git checkout command with its `-b` option to create |
227 | a branch and check it out with a single command. | |
228 | ||
e5ac1217 | 229 | The options `--contains`, `--merged` and `--no-merged` serve three related |
9a7ea2b1 LH |
230 | but different purposes: |
231 | ||
232 | - `--contains <commit>` is used to find all branches which will need | |
233 | special attention if <commit> were to be rebased or amended, since those | |
234 | branches contain the specified <commit>. | |
235 | ||
236 | - `--merged` is used to find all branches which can be safely deleted, | |
237 | since those branches are fully contained by HEAD. | |
238 | ||
239 | - `--no-merged` is used to find branches which are candidates for merging | |
240 | into HEAD, since those branches are not fully contained by HEAD. | |
1e2ccd3a | 241 | |
b85e6c5f NS |
242 | SEE ALSO |
243 | -------- | |
244 | linkgit:git-check-ref-format[1], | |
245 | linkgit:git-fetch[1], | |
bb35f35e JN |
246 | linkgit:git-remote[1], |
247 | link:user-manual.html#what-is-a-branch[``Understanding history: What is | |
248 | a branch?''] in the Git User's Manual. | |
b85e6c5f | 249 | |
7fc9d69f JH |
250 | GIT |
251 | --- | |
9e1f0a85 | 252 | Part of the linkgit:git[1] suite |