Skip to content

lab 38 Review the Cloned Repository


Look at the cloned repository

Let’s take a look at the cloned repository.


cd cloned_hello


$ cd cloned_hello
$ ls

You should see a list of all the files in the top level of the original repository (README, Rakefile and lib).

Review the Repository History


git hist --all


$ git hist --all
* c46c56e 2018-09-28 | Updated Rakefile (HEAD -> master, origin/master, origin/greet, origin/HEAD) [Jim Weirich]
* 0ccac93 2018-09-28 | Hello uses Greeter [Jim Weirich]
* a5ff572 2018-09-28 | Added greeter class [Jim Weirich]
* 5c40874 2018-09-28 | Added README [Jim Weirich]
* 191f0c6 2018-09-28 | Added a Rakefile. [Jim Weirich]
* ef98cae 2018-09-28 | Moved hello.rb to lib [Jim Weirich]
* e1e08fd 2018-09-28 | Add an author/email comment [Jim Weirich]
* 7bf0bf1 2018-09-28 | Added a comment (tag: v1) [Jim Weirich]
* 9cf3f21 2018-09-28 | Added a default value (tag: v1-beta) [Jim Weirich]
* 94e1b8b 2018-09-28 | Using ARGV [Jim Weirich]
* f656098 2018-09-28 | 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

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.