You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: book/03-git-branching/sections/branch-management.asc
+14-14Lines changed: 14 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,10 +2,10 @@
2
2
=== 分支管理
3
3
4
4
(((branches, managing)))
5
-
Now that you've created, merged, and deleted some branches, let's look at some branch-management tools that will come in handy when you begin using branches all the time.
Notice the `*` character that prefixes the `master` branch: it indicates the branch that you currently have checked out (i.e., the branch that `HEAD` points to).
19
-
This means that if you commit at this point, the `master` branch will be moved forward with your new work.
20
-
To see the last commit on each branch, you can run `git branch -v`:
testing 782fd34 add scott to the author list in the readmes
28
28
----
29
29
30
-
The useful `--merged` and `--no-merged` options can filter this list to branches that you have or have not yet merged into the branch you're currently on.
31
-
To see which branches are already merged into the branch you're on, you can run `git branch --merged`:
Because you already merged in `iss53` earlier, you see it in your list.
41
-
Branches on this list without the `*` in front of them are generally fine to delete with `git branch -d`; you've already incorporated their work into another branch, so you're not going to lose anything.
0 commit comments