@@ -172,8 +172,30 @@ Since we're keeping things simple this time around, in the *'Local Destination'*
172172and click * 'Finish'* .
173173![ ] ( images/screenshots/09-EgitLocalDestination.png?raw=true )
174174
175+ Let's take a look at what was cloned, the first command navigates us to the correct starting place for the commmands
176+ to follow, but as long as the path given to any of the commands resolves correctly you can do this anyway you like:
177+ ```
178+ cd ~/Studio/Dev
179+
180+ tree test-github-clone/
181+ ```
182+ ![ ] ( images/screenshots/10-TreeOnTestProject.png?raw=true )
183+ As you can see there is currently only the README.md file in the root of the project, this might change
184+ as we test a few concepts but as long as you have the directory and some files you're good.
185+ 186+ That view of the project is as much as we are really interested in, but of course there is a lot more to a git project
187+ and if you interested to see the full scope of what we have cloned you can run the following command:
188+ ```
189+ tree -lsa test-github-clone/
190+ ```
191+ ![ ] ( images/screenshots/11-FullTreeOnTestProject.png?raw=true )
192+ 175193## Workspace v Project Directory
176- > It's time we had a chat about something...
194+ > Before we go any further, if you've paid attention and particularly if you're
195+ > familiar with Eclipse you will have noticed that we did not clone the
196+ > Project into our Workspace, we will be importing the Project into
197+ > our Workspace but to prevent git detecting and potentially including
198+ > any Eclipse specific files we'll keep Eclipse away from the Project directory.
177199
178200
179201### Step 3: Add a local git project
0 commit comments