Okay, welcome back. In this demonstration we're going to do the same as the first, but instead we're going to assume that our project directory on the file system locally has already been populated with our programming assets, or coding files, So, lets start. So, within Bitbucket we'll create another repository. This time we'll call it CADemo2. Again, make sure that the version control system is set to Git and click the Create Repository button. Again, Bitbucket in the background has gone ahead and successfully created our new repository, and it's empty. So last time, we took the https git clone URL, and then jumped into the terminal. We're not going to do this, this time. Instead, this time from within the terminal, we're going to create a directory. So this time we'll create cademo2. We'll navigate into it. And we'll copy the file that we created in the other demonstration from cademo into this directory. So we don't want to copy the directory, we want to copy the file, which is index.html. Okay. Listing the contents of this directory, we've got index.html. We'll run git init to initialize the directory as being version controlled. Do file listing again. You can see here that the output of this command was to generate our special .git directory. And this is the magic where we connect this directory back up to our new CADemo2 git repository. 

By running the command git remote add origin, because we're setting the repository as the origin. We'll jump back into our new repository, and this time we'll just copy this portion back into our terminal. Paste. Enter. Okay, so that's successfully set the new repository within Bitbucket as the origin. And then we can simply push our contents up by doing a git push -u to the origin in the master branch. Enter. Okay, apologies. We haven't actually staged or committed anything. So if we did a git status, you'll see that we've got an untracked file. So we need to do a git add index.html, then commit it, or do git status again. You can see now that we've got our new file. Here, we'll do a git commit, set the message, this time we'll use the message initial commit. Enter. And this time we run our command git push -u to the origin in the master branch. And excellent. So let's push up. So we jump back into Bitbucket. We'll do a reload. And again, we've successfully pushed our changes up. So, the difference of this demonstration was instead of cloning down into an empty directory, we simulated an existing software directory with assets within it, and then we committed to our local repository and pushed up to the origin. Okay, that completes this lecture. Go ahead and close it, and we'll see you shortly in the next one.