Okay, welcome back. In this next demonstration, we're going to do the same thing again, but this time we're going to use a third-party desktop client, the GitHub Desktop Client, in fact, to manage our repository. So let's get started. Again, the first thing we'll do is we'll create a new repository. We'll call it CADemo3, ensuring it's a Git repository, clicking the create repository button. And then we've successfully created the repository. This time we'll select HTTPS and we'll copy the URL, copy. At this time, we'll use the GitHub Desktop Client. And then we'll add in the repository, since we're going to use the client to manage it. Under File, we'll clone the repository. Specify URL, which we just copied. And we're going to put it into our demos folder. Click Clone, and the Desktop Client clones it and manages it for us. So if we jump back into the terminal, and we now do a directory listing in our demos folder, you can see again that we've got a new local repository, this time named CADemo3. And it's got our special .git directory. So again, we'll copy an existing file in one of the previous directories. C-A demo slash index, into this directory. And we'll do a git status. And you can see that it's showing up as an untracked file. Okay, this time as mentioned, we're going to use the GitHub Desktop Client to manage this.

 And you can see here that Index.html is showing up as a changed file with this plus icon, which means we need to stage it and then commit it. So the staging will be done for us in the background, but we'll give it an initial message. This time, we'll call it first commit of project. We'll commit to master as our local repository. And then we can publish the branch. We'll push it up to the remote repository being held within BitBucket. So let's click publish. The pushing is going up to the origin. And that's now completed successfully. So if we jump back into BitBucket, again if we reload, you can see our file. Now if we jump back into the terminal and what we'll do is we'll open up this directory inside Visual Code. We'll make a small edit. And we'll jump back into the GitHub client. And you'll notice here now that the Index.html file is showing that it's been changed, as per this icon, and it's clever enough to actually show the lines between the last commit and the current change. So here is our most recent edit on this file. So again, we can add a message. We can commit to master in the local repository. And here we can push back up to the remote repository. You see that this one file or one commit. And at the same time, it's going to download any changes that have been pushed into the remote repository that we don't have locally. So finally, jumping back into BitBucket, we look at the commits. You can see that this is our latest commit that we just pushed up. If we jump into the commit, here again you can see our change. Okay, that completes this demonstration. Go ahead and close it, and we'll see you shortly in the next one.