Review the Cloned Repository

Goals

• Learn about branches on remote repositories.

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
* e0cc19e 2020-06-20 | Updated Rakefile (HEAD -> master, origin/master, origin/greet, origin/HEAD) [Jim Weirich]
* 046088a 2020-06-20 | Hello uses Greeter [Jim Weirich]
* 3db0ffe 2020-06-20 | Added greeter class [Jim Weirich]
* 8d90176 2020-06-20 | Added README [Jim Weirich]
* 5aec14d 2020-06-20 | Added a Rakefile. [Jim Weirich]
* 721b979 2020-06-20 | Moved hello.rb to lib [Jim Weirich]
* 907a445 2020-06-20 | Add an author/email comment [Jim Weirich]
* 4254c94 2020-06-20 | Added a comment (tag: v1) [Jim Weirich]
* c8b3af1 2020-06-20 | Added a default value (tag: v1-beta) [Jim Weirich]
* 30c2cd4 2020-06-20 | Using ARGV [Jim Weirich]
* 4445720 2020-06-20 | 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.