Skip to content

lab 38 Review the Cloned Repository

Goals

Look at the cloned repository

Let’s take a look at the cloned repository.

Execute:

cd cloned_hello
ls

Output:

$ cd cloned_hello
$ ls
README
Rakefile
lib

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

Execute:

git hist --all

Output:

$ git hist --all
* ff7c118 2019-11-01 | Updated Rakefile (HEAD -> master, origin/master, origin/greet, origin/HEAD) [Jim Weirich]
* 2a262be 2019-11-01 | Hello uses Greeter [Jim Weirich]
* 413c34f 2019-11-01 | Added greeter class [Jim Weirich]
* 099ccd0 2019-11-01 | Added README [Jim Weirich]
* ed35144 2019-11-01 | Added a Rakefile. [Jim Weirich]
* 4421854 2019-11-01 | Moved hello.rb to lib [Jim Weirich]
* 185fc95 2019-11-01 | Add an author/email comment [Jim Weirich]
* 4d578d4 2019-11-01 | Added a comment (tag: v1) [Jim Weirich]
* dc1d42f 2019-11-01 | Added a default value (tag: v1-beta) [Jim Weirich]
* 9a1c494 2019-11-01 | Using ARGV [Jim Weirich]
* 063b40e 2019-11-01 | First Commit [Jim Weirich]

You should now see a list of 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 a number of strangely named branches (origin/master, origin/greet and origin/HEAD). We’ll talk about them in a bit.