mirror/pcottle.learnGitBranching
1
0
Fork 0
mirror of https://github.com/pcottle/learnGitBranching.git synced 2025-08-02 00:54:40 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

Error in git clone behavior Pull Request #152

Browse source
This commit is contained in:
Peter Cottle 2013-12-22 22:23:24 -08:00
parent 2c982b704b
commit 316dd916bd
1 changed files with 5 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

8
src/levels/remote/tracking.js
View file

@ -37,11 +37,13 @@ exports.level = {
"",
"You may be wondering how this property got set on the `master` branch when you didn't run any commands to specify it. Well, when you clone a repository with git, this property is actually set for you automatically. ",
"",
"During a clone, git creates a remote branch for every branch on the remote (aka branches like `o/master`) and then, for each remote branch, creates a local branch to *track* that remote branch (aka `master`). Thats why you may have seen the following command output:",
"During a clone, git creates a remote branch for every branch on the remote (aka branches like `o/master`). It then creates a local branch that tracks the currently active branch on the remote, which is `master` in most cases.",
"",
" local branch \"master\" set to track remote branch \"o/master\"",
"Once git clone is complete, you only have one local branch (so you aren't overwhelmed) but you can see all the different branches on the remote (if you happen to be very curious). It's the best of both worlds!",
"",
"When running `git clone`."
"This also explains why you may see the following command output when cloning:",
"",
" local branch \"master\" set to track remote branch \"o/master\""
]
}
},