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
* d9d52f1 2020-05-30 | Updated Rakefile (HEAD -> master, origin/master, origin/greet, origin/HEAD) [Jim Weirich]
* 7226fee 2020-05-30 | Hello uses Greeter [Jim Weirich]
* bd0e5fa 2020-05-30 | Added greeter class [Jim Weirich]
* 32cb785 2020-05-30 | Added README [Jim Weirich]
* 128a484 2020-05-30 | Added a Rakefile. [Jim Weirich]
* a3cf03d 2020-05-30 | Moved hello.rb to lib [Jim Weirich]
* 96c1fec 2020-05-30 | Add an author/email comment [Jim Weirich]
* 9811d9e 2020-05-30 | Added a comment (tag: v1) [Jim Weirich]
* 3344f03 2020-05-30 | Added a default value (tag: v1-beta) [Jim Weirich]
* 3cb4c15 2020-05-30 | Using ARGV [Jim Weirich]
* dfb5614 2020-05-30 | 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.