Up and Running with Git Transcripts
Chapter: Our first git repository
Lecture: Creating a hosted repository

Login or purchase this course to watch this video and the rest of the course contents.
0:00 Alright. It is time to build.
0:02 Let's jump over to git hub and get started.
0:06 Here. We are in my github account.
0:08 I'm already logged in, we want to create a new repository,
0:11 you can see some stuff here about how other people have interacted with me or people
0:16 I'm following are doing things but where we want to go is just over to the
0:20 new section and we're going to create a new repository.
0:23 I could both do this in the talk python organization,
0:27 make it formal, I could do it on my personal account here and I'll do
0:30 it that way. We're going to create some kind of app.
0:33 I'm thinking a flask app that tells us tech jokes,
0:37 how about that? That sounds like a lot of fun.
0:40 So let's call it something like funny web,
0:46 we can name it whatever we want.
0:47 It's going to get converted to a Url type of thing.
0:50 This will be sample app run course.
0:55 You know, I could create a public and probably normally I would,
0:57 but since it's just gonna be around for a little while as we do this project
1:01 I'm going to make it private.
1:03 Who knows? Maybe I'll make it public in case you want to run across it
1:05 later. Now again, when you get to git hub,
1:09 there are many things layered on top of git it will help you get started or
1:14 provide other workflows. One of the ideas is to have a read me file,
1:17 this isn't really a good thing,
1:18 but it is a way to help kickstart how others can view your project.
1:23 So you definitely want to read me file if it's going to be public at least
1:27 the other thing we're going to talk more about this in this chapter is certain files
1:31 should never ever be checked into source control.
1:35 That includes files that might have passwords in them.
1:39 Never checked passwords into source control.
1:41 Store them in some other way.
1:43 It could also just be really large files like maybe I'm working on a website that
1:47 does stuff with video and there's mp4's hanging around in the directories and those
1:53 we want to put there but we don't want to commit those huge files potentially back
1:58 into github. So that's what this git ignored is about.
2:01 And you should pick something that most closely aligns with your language.
2:04 You can see there are many languages we are going to use python because we're gonna
2:09 do flask and we can choose a license.
2:12 If you do not choose a license that means you are not creating something open source
2:17 It might be source open but it doesn't convey permissions to other people to use
2:23 it. So if you want people to use it you can give it like an
2:26 MIT license or something like that.
2:28 Alright, let's create there. We have it.
2:31 Here's our repository, it lives up my user name /the name.
2:34 We gave the repository up there here,
2:36 you can see the contents of the read me automatically show up and there's all this
2:40 github stuff that we don't really care about.
2:42 We've got it created now what?