Join James Williamson for an in-depth discussion in this video Creating a new repository, part of GitHub for Web Designers.
Now that we know a little bit more about Git, it's time to turn our attention to focus on GitHub. So in this chapter, we're going to focus on the basics of GitHub, and some of the things that you can accomplish directly on the site. So, I'm navigated to GitHub, and I've signed into my jameswillweb2 account. And, I'm ready to start working. Now, if I take a look at my account. And I go to my repo's, I can see that I have to git basics repo that we have been working on so far in the course, but what if I wanted to add a new repo? Well, there are a lot of different ways to do that.
If I go back, to say the homepage, if you will, of GitHub. I can see they've done it in the lower right hand corner. And there's a little link for a new repository. Right down here there's a create a repository link. That's more of an article. Kind of walks you through this process. But even in that there's a link to create one. If I go up to my account, I notice there's a little plus symbol beside that. And when I click on that, here's a link to create a new repository. And if I'm in the account view itself, and I go to repositories, there's a link to create a new repository.
I think you get the idea. Almost everywhere you are inside of GitHub, you can create a brand new repository. Now this isn't going to do anything for us local just yet. This is going to create a repository on the site. So I'm going to go ahead and click new. It doesn't matter where you do it at. We're just going to go ahead and create a brand new repository. The first thing it's going to ask us to do is create a repository name. And I'm just going to call this one github basics. See what I did there? So, github basics. And the description for this one, is remote.
Repo, to help me test out my GitHub skills. I bet you couldn't see that coming, right, from a mile away. Okay, now, this one's going to be public as well. Now there's a couple of things down here, that we're actually going to do in later movies in this chapter. So we're not going to do them right now. Except for a license. We're going to do that. So we're not going to do a get ignore, we're not going to do a Read Me. But I do want to add a license to this. Github recommends that you add a license to any of your public repositories. If it's a private repository, if it's a private repo and it's just your project, that's one thing.
But any repo that you put on your get hub free account, is going to be public, meaning anybody can go in and download it. So it's really helpful. If you add a license. Now the nice thing about this, is they have a lot of open source licenses available. They have the MIT license that I see all over the place these days. The GPL 2, the Apache version 2. And most of these are open source libraries. We have Creative Commons Universal, which is one of my favorite ones. And there is a place on GitHub site, where you can go to read more about these licenses, so that you know what terms you're licensing your content under.
So that it's going to be used in the way that you intend it to be used. All right? So I'm just going to use the creative comments 1.0 universal. I'm going to turn off Initialize this repository with a Read Me. I'm going to turn that off. And the reason I'm going to turn that off, is because I'm going to create that manually in the next exercise. All right I'm going to go ahead and create the repo. And we've seen this before. If you remember in the last chapter, when we were doing our push we came in and created a repository really quickly, a remote one, and we had all of this sort of quick set up stuff. So of course, we just created this remote repository. it doesn't have any files in it, other than the license that we gave it, which isn't.
Really a separate file but we haven't really added any files to it yet. We don't have a Read Me, we don't have a Get Ignore file which I'll talk about in just a little bit. So in this code view, that we have over here on the right-hand side there's really nothing to see. So we need to start adding some files to it and we'll start in the next movie by adding a Read Me file.
- Creating an account
- Installing GitHub
- Git basics
- Adding files to Git
- Checking differences
- Creating, switching, and updating branches
- Creating a new GitHub repository
- Managing files with the GitHub client
- Working with collaborators
Skill Level Intermediate
Q: Why can't I create a .nojekyll file?
<!--[if gte mso 10]> <![endif]--> <p>A: Depending upon your operating system and platform, you may have certain restrictions which make it impossible to create a .nojekyll file through Finder or Windows Explorer. Usually you’ll receive an error message that informs you that files starting with a “.” are system files and that you lack the permissions necessary to create one. If that’s the case, you’ll need to create the file through a Terminal window or bash prompt. Here’s how you do it:<br /> </p> <blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"> <div> <div id="pastingspan1">1.<span style="white-space:pre"> </span>Open a Terminal window if you’re on a Mac, or the bash prompt from the Github client if you’re on Windows. </div> </div> <div> <div id="pastingspan1">2.<span style="white-space:pre"> </span>Navigate to the repository’s root directory.</div> </div> <div> <div id="pastingspan1">3.<span style="white-space:pre"> </span>Type the following at the prompt: $ touch .nojekyll</div> </div> <div> <div id="pastingspan1">4.<span style="white-space:pre"> </span>That’s it! The next time you make a commit and push to the master branch you should see your new .nojekyll file.</div> </div> </blockquote>