[MUSIC]

Workspaces is one of my favorite features here at Treehouse.

It combines a terminal, a file browser and a text editor all into one and

even let's me run a server like when I'm using Django and Rails and see the output.

I've been lucky enough to use it almost everything I've taught and

I have no plans on stopping that anytime soon.

One of the questions I've been asked several times,

though is if you have to give up workspaces to be able to use GitHub.

This question has a surprisingly tricky answer.

If you're to the point where you want to put your work up on GitHub, you're

probably to the point where you should be working locally most of the time.

Development will probably be faster for

you, you'll be able to use your favorite tools and some workflows will work better

on your computer than they will on the Workspaces server, but you don't have to.

If you love Workspaces or need to be able to work on something from any computer

that's connected to the internet, you can stick with Workspaces and

take full advantage of GitHub.

Let's go to the source, Workspaces and see how to use it with GitHub.

Just like working with GitHub on your own computer,

the first thing you probably wanna do is create a repo.

Now, I can do this in Workspaces or I can do it on GitHub itself.

I don't really have a preferred way, so

I kinda just do whichever one seems more expedient at the moment.

So, I'm gonna start on GitHub.

So here, I am on github.com as you can already see.

And up here on the top, there is this plus button.

And if you're on your profile page,

there's also this newer repository button down here.

So I'm gonna click the create new and I'm gonna choose new repository and the button

might be in a different spot, just because GitHub does change their UI around.

I always end up having to look for it.

If you can't find it, there is a link down here to Help and

they have really good help documentation.

So, I need to name this repository.

I think I'm going to make a little reminder script.

Like something that I can use just to, hey, remind me to take out the trash.

Remind me to write that documentation.

Remind me to release a course.

So I'm gonna name that rememberer, cuz it does my remembering for me.

If you don't have a name, then GitHub actually gives you one,

which is kinda cool.

So potential-octo-adventure, that's actually a really great name.

Anyway, so for the description,

I'm gonna give it a quick description of what it does.

Lots of times people leave projects without a description.

That just really annoys me.

I'm gonna say, remembers things for you so

you don't have to and I'm gonna make the repository Public.

We have to pay for private repos.

If you don't have them, then you'll have to upgrade your account.

I don't care if anybody sees those codes, I'm gonna make it public.

I'm gonna go ahead and initialize it with a README,

just so there's a file in there and I'm going to, this is going to be python.

So, I'm gonna add a python get ignore.

And for licensing, I'm a big fan of the BSD 3-clause, but the MIT.

I mean, all the licenses are okay, so pick whichever one you want.

So I'm gonna do that, just because I wanna get this stuff in there.

So I'm gonna create that repository and cool.

So there's my repository and up here for cloning,

there's an address here and you can choose to do it between HTTPS or SSH.

The HTTPS one is a little bit easier,

you don't have to deal with SSH key and a passphrase.

So, I'm just gonna go ahead and copy that to my clipboard and

then I'm gonna come over here to Workspaces.

And I've already clicked the new Workspace button, so I'm gonna go ahead and

make a new Workspace now and I'm gonna say, it's the Rememberer Project and

I'm building this in Python.

So, I'm gonna put Python there.

Now of course, whatever language you want to use, go for it.

You don't have to do this as Python.

You can do this as anything you want and then I'm gonna hit create Workspace.

So, awesome.

Now, we have a great Workspace.

Let it spin up and then let's see.

Down here in this bottom part, this is my terminal.

So down here's where I wanna clone, I wanna check out my project.

So I'm gonna say, git clone and

then I'm gonna paste in the repository

address that GitHub gave me, press Enter.

Wait for a second and then I'm gonna Refresh the sidebar and

looks like I have a Rememberer Project.

So, that's pretty cool.

I have my License file.

My God, shrink that down.

I have my LICENSE file and I have my README.md.

So, great.

There's everything that I was looking form, but

this README.md is really bare because it just started.

It doesn't really have anything impressive in it.

So, I'm gonna fill this out a little bit more.

Lots of times when I'm first starting on a project,

I like to do what's called read me driven development and

the idea is that basically, you write docs about how your project works and

then you write your code, so that your docs are telling the truth.

No one likes lying documentation.

So let's say, Usage and we'll say,

'remem take out the cat litter' and

that will add a new item to be remembered and

'remem --list'- print out the list of things to remember.

'Remem --delet 2'- delete

the item with index 2 and 'remem

--next'- print out the next thing to do.

That's a pretty good README.md.

I obviously, have quite a bit of work ahead of me.

But I have made a change, so I need to make a commit.

So, I'm going to come back down here to my terminal and

let's do git status and fatal.

Not a get repository, that's right, because rememberer is the git repository.

So, let's get into rememberer and

now, we can do git init.

That's not what I wanted to do, I wanted to do git status.

There we go.

So, I have this README.md file that has been changed.

So, I need to add that change in.

So I'm gonna add the READMe.md file and them I'm gonna do a commit and

I'll say, "add example usage to README".

And so now git doesn't know who I am,

so you might have to add this yourself.

And basically, you just want to copy and do what git has here.

So, I'm gonna do git config user.email "kenneth@teamtreehouse.com" and

you'll notice that git lets me do this --global and I'm leaving off --global.

The reason for that is the --global goes to the system wide git so

that it remembers who you are.

The system wide git isn't going to be the same from workspace to workspace.

So I want this to remember me just for the repo and

user.name will be "Kenneth Love".

So now, let's check out git status.

So our thing was added, but we haven't committed it yet.

So let's rerun our commit, cool.

So, we added the example usage to the README.md and

now I'm gonna go ahead and push these up to GitHub.

So I will get push origin master, which is the default and

now I have to put in a username.

GitHub is going to ask you for your username and

your password every single time and that's because GitHub on

Workspaces doesn't store your identity, which is a good thing.

It's fine, we don't want our identity store on Workspaces.

So while it's annoying to have to type those in, it's great for privacy.

So, it's okay.

It makes pushing a little bit tedious, what I normally do if I'm going to be

working in Workspaces is make as many commits as I can before I push and

I just push like when I'm pretty much done with something.

You probably don't want to do that with a team,

because your team is probably going to want updates more often.

But if you're working on a feature branch by yourself, it's not that big of a deal.

So, let's check out GitHub and see if my changes came through.

So, we have two comments.

And if I look at the README.md, then yeah, I have my stuff.

It's not formatted great, but it's there.

So now, it's time to actually go build this thing.

I probably wanna go fix my README.md, so

that it comes through in a better format, but it all works.

So I'm gonna go work on this,

I don't wanna keep the rest of you from the rest of your day.

So, I'll do that on my own and

you can go build whatever it is that you need to build.

Like I said earlier,

you probably want to work locally by the time you want to put work up on GitHub.

Go for it.

Installing Git on you computer is pretty straightforward.

But whether you use your machine or Workspaces, the important part

is building up projects on GitHub and helping others with their projects.

If you want to learn more about Git or GitHub,

check out our courses on each of those.

A link to them both in the teachers notes.

Good luck and I can't wait to see what you built.