lab 38 Review the Cloned Repository
- Learn about branches on remote repositories.
Look at the cloned repository 01
Let’s take a look at the cloned repository.
cd cloned_hello ls
$ cd cloned_hello $ ls README Rakefile lib
You should see a list of all the files in the top level of the original repository (
Review the Repository History 02
git hist --all
$ git hist --all * b818028 2014-10-25 | Updated Rakefile (HEAD, origin/master, origin/greet, origin/HEAD, master) [Jim Weirich] * b790264 2014-10-25 | Hello uses Greeter [Jim Weirich] * 0a576ce 2014-10-25 | Added greeter class [Jim Weirich] * 6fd9eff 2014-10-25 | Added README [Jim Weirich] * 14ba469 2014-10-25 | Added a Rakefile. [Jim Weirich] * 4b249b3 2014-10-25 | Moved hello.rb to lib [Jim Weirich] * bfd1408 2014-10-25 | Add an author/email comment [Jim Weirich] * a1189df 2014-10-25 | Added a comment (tag: v1) [Jim Weirich] * 6083cb8 2014-10-25 | Added a default value (tag: v1-beta) [Jim Weirich] * b24f3ff 2014-10-25 | Using ARGV [Jim Weirich] * cf466b4 2014-10-25 | First Commit [Jim Weirich]
You should now see a list of the all the commits in the new repository, and it should (more or less) match the history of commits in the original repository. The only difference should be in the names of the branches.
Remote branches 03
You should see a master branch (along with HEAD) in the history list. But you will also have number of strangely named branches (origin/master, origin/greet and origin/HEAD). We’ll talk about them in a bit.