git branch ¶
See also
git branch ¶
git branch
affiche toutes les branches du dépôt local.
git branch [nom-de-branche] ¶
git branch [nom-de-branche]
crée une nouvelle branche.
git branch -m [nom-de-branche] [nouveau-nom] ¶
git branch -m [nom-de-branche] [nouveau-nom]
change le nom de la branche.
Create a new branch ¶
To create a new branch and making it the current working branch
git branch new-branch
git checkout new branch
You can do the same with only one command:
git checkout -b new-branch
Delete a branch ¶
git branch -D <branch>
Find Branches ¶
git branch --contains <commit>
This command will show all branches that contain a particular commit.
Rename Branches Locally ¶
git branch -m old-name new-name
If you want to rename the currently checked out branch, you can shorten this command to the following form:
git branch -m new-name
For more: git help branch
Rename Branches Remotely ¶
In order to rename a branch remotely, once you renamed your branch locally, you need to first remove that branch remotely and then push the renamed branch again:
git push origin old-name
git push origin new-name
git help branch ¶
1GIT-BRANCH(1) Git Manual GIT-BRANCH(1)
2
3NAME
4 git-branch - List, create, or delete branches
5
6SYNOPSIS
7 git branch [--color[=<when>] | --no-color] [-r | -a]
8 [--list] [-v [--abbrev=<length> | --no-abbrev]]
9 [--column[=<options>] | --no-column] [--sort=<key>]
10 [(--merged | --no-merged) [<commit>]]
11 [--contains [<commit]] [--no-contains [<commit>]]
12 [--points-at <object>] [--format=<format>] [<pattern>...]
13 git branch [--track | --no-track] [-f] <branchname> [<start-point>]
14 git branch (--set-upstream-to=<upstream> | -u <upstream>) [<branchname>]
15 git branch --unset-upstream [<branchname>]
16 git branch (-m | -M) [<oldbranch>] <newbranch>
17 git branch (-c | -C) [<oldbranch>] <newbranch>
18 git branch (-d | -D) [-r] <branchname>...
19 git branch --edit-description [<branchname>]
20
21DESCRIPTION
22 If --list is given, or if there are no non-option arguments, existing branches are listed; the current branch will be highlighted with an asterisk. Option -r causes the remote-tracking branches to be listed, and option -a
23 shows both local and remote branches. If a <pattern> is given, it is used as a shell wildcard to restrict the output to matching branches. If multiple patterns are given, a branch is shown if it matches any of the patterns.
24 Note that when providing a <pattern>, you must use --list; otherwise the command is interpreted as branch creation.
25
26 With --contains, shows only the branches that contain the named commit (in other words, the branches whose tip commits are descendants of the named commit), --no-contains inverts it. With --merged, only branches merged into
27 the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With --no-merged only branches not merged into the named commit will be listed. If the <commit> argument is missing it
28 defaults to HEAD (i.e. the tip of the current branch).
29
30 The command’s second form creates a new branch head named <branchname> which points to the current HEAD, or <start-point> if given.
31
32 Note that this will create the new branch, but it will not switch the working tree to it; use "git checkout <newbranch>" to switch to the new branch.
33
34 When a local branch is started off a remote-tracking branch, Git sets up the branch (specifically the branch.<name>.remote and branch.<name>.merge configuration entries) so that git pull will appropriately merge from the
35 remote-tracking branch. This behavior may be changed via the global branch.autoSetupMerge configuration flag. That setting can be overridden by using the --track and --no-track options, and changed later using git branch
36 --set-upstream-to.
37
38 With a -m or -M option, <oldbranch> will be renamed to <newbranch>. If <oldbranch> had a corresponding reflog, it is renamed to match <newbranch>, and a reflog entry is created to remember the branch renaming. If <newbranch>
39 exists, -M must be used to force the rename to happen.
40
41 The -c and -C options have the exact same semantics as -m and -M, except instead of the branch being renamed it along with its config and reflog will be copied to a new name.
42
43 With a -d or -D option, <branchname> will be deleted. You may specify more than one branch for deletion. If the branch currently has a reflog then the reflog will also be deleted.
44
45 Use -r together with -d to delete remote-tracking branches. Note, that it only makes sense to delete remote-tracking branches if they no longer exist in the remote repository or if git fetch was configured not to fetch them
46 again. See also the prune subcommand of git-remote(1) for a way to clean up all obsolete remote-tracking branches.
47
48OPTIONS
49 -d, --delete
50 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.
51
52 -D
53 Shortcut for --delete --force.
54
55 --create-reflog
56 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
57 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.
58
59 -f, --force
60 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
61 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).
62
63 -m, --move
64 Move/rename a branch and the corresponding reflog.
65
66 -M
67 Shortcut for --move --force.
68
69 -c, --copy
70 Copy a branch and the corresponding reflog.
71
72 -C
73 Shortcut for --copy --force.
74
75 --color[=<when>]
76 Color branches to highlight current, local, and remote-tracking branches. The value must be always (the default), never, or auto.
77
78 --no-color
79 Turn off branch colors, even when the configuration file gives the default to color output. Same as --color=never.
80
81 -i, --ignore-case
82 Sorting and filtering branches are case insensitive.
83
84 --column[=<options>], --no-column
85 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.
86
87 This option is only applicable in non-verbose mode.
88
89 -r, --remotes
90 List or delete (if used with -d) the remote-tracking branches.
91
92 -a, --all
93 List both remote-tracking branches and local branches.
94
95 -l, --list
96 List branches. With optional <pattern>..., e.g. git branch --list 'maint-*', list only the branches that match the pattern(s).
97
98 -v, -vv, --verbose
99 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>).
100
101 -q, --quiet
102 Be more quiet when creating or deleting a branch, suppressing non-error messages.
103
104 --abbrev=<length>
105 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.
106
107 --no-abbrev
108 Display the full sha1s in the output listing rather than abbreviating them.
109
110 -t, --track
111 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
112 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.
113
114 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
115 given. Set it to always if you want this behavior when the start-point is either a local or remote-tracking branch.
116
117 --no-track
118 Do not set up "upstream" configuration, even if the branch.autoSetupMerge configuration variable is true.
119
120 --set-upstream
121 As this option had confusing syntax, it is no longer supported. Please use --track or --set-upstream-to instead.
122
123 -u <upstream>, --set-upstream-to=<upstream>
124 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.
125
126 --unset-upstream
127 Remove the upstream information for <branchname>. If no branch is specified it defaults to the current branch.
128
129 --edit-description
130 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.
131
132 --contains [<commit>]
133 Only list branches which contain the specified commit (HEAD if not specified). Implies --list.
134
135 --no-contains [<commit>]
136 Only list branches which don’t contain the specified commit (HEAD if not specified). Implies --list.
137
138 --merged [<commit>]
139 Only list branches whose tips are reachable from the specified commit (HEAD if not specified). Implies --list, incompatible with --no-merged.
140
141 --no-merged [<commit>]
142 Only list branches whose tips are not reachable from the specified commit (HEAD if not specified). Implies --list, incompatible with --merged.
143
144 <branchname>
145 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.
146
147 <start-point>
148 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.
149
150 <oldbranch>
151 The name of an existing branch to rename.
152
153 <newbranch>
154 The new name for an existing branch. The same restrictions as for <branchname> apply.
155
156 --sort=<key>
157 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
158 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)
159 first, then local branches and finally remote-tracking branches. See git-config(1).
160
161 --points-at <object>
162 Only list branches of the given object.
163
164 --format <format>
165 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).
166
167CONFIGURATION
168 pager.branch is only respected when listing branches, i.e., when --list is used or implied. The default is to use a pager. See git-config(1).
169
170EXAMPLES
171 Start development from a known tag
172
173 $ git clone git://git.kernel.org/pub/scm/.../linux-2.6 my2.6
174 $ cd my2.6
175 $ git branch my2.6.14 v2.6.14 (1)
176 $ git checkout my2.6.14
177
178 1. This step and the next one could be combined into a single step with "checkout -b my2.6.14 v2.6.14".
179
180 Delete an unneeded branch
181
182 $ git clone git://git.kernel.org/.../git.git my.git
183 $ cd my.git
184 $ git branch -d -r origin/todo origin/html origin/man (1)
185 $ git branch -D test (2)
186
187 1. Delete the remote-tracking branches "todo", "html" and "man". The next fetch or pull will create them again unless you configure them not to. See git-fetch(1).
188 2. Delete the "test" branch even if the "master" branch (or whichever branch is currently checked out) does not have all commits from the test branch.
189
190NOTES
191 If you are creating a branch that you want to checkout immediately, it is easier to use the git checkout command with its -b option to create a branch and check it out with a single command.
192
193 The options --contains, --no-contains, --merged and --no-merged serve four related but different purposes:
194
195 · --contains <commit> is used to find all branches which will need special attention if <commit> were to be rebased or amended, since those branches contain the specified <commit>.
196
197 · --no-contains <commit> is the inverse of that, i.e. branches that don’t contain the specified <commit>.
198
199 · --merged is used to find all branches which can be safely deleted, since those branches are fully contained by HEAD.
200
201 · --no-merged is used to find branches which are candidates for merging into HEAD, since those branches are not fully contained by HEAD.
202
203SEE ALSO
204 git-check-ref-format(1), git-fetch(1), git-remote(1), “Understanding history: What is a branch?”[1] in the Git User’s Manual.
205
206GIT
207 Part of the git(1) suite
208
209NOTES
210 1. “Understanding history: What is a branch?”
211 file:///usr/share/doc/git/html/user-manual.html#what-is-a-branch
212
213Git 2.21.0 02/26/2019 GIT-BRANCH(1)