Starting a project with an issue - GitHub Tutorial

- [Instructor] In addition to creating items in our projects, we can also create issues and then add them to projects at a later time. So sometimes when you're working on something, you aren't just really working within issues. You're kind of not necessarily concerned with the project, but at some point you do want to tie those things if you want to track them there. So I'm going to go just to the issues here and create a new issue. Now here I want to go ahead and add a license to this project. So I'm going to assign this as well. So I'll say add a license to project and I'm going to assign this once again to me and Jojo I'll go ahead and fill out some of the rest of this stuff. So for projects, I will say this is GitHub projects, the one that I've been working on. The milestone will still be set up because it is something related to that as well. And that's all I can do for right now, right here. And once I add it to projects, this will now become an item that I can track as well over here in my regular projects section. So let's go ahead though and add a comment here. Again, it's going to take a little bit to get used to adding that at sign, but it does really help because what will happen also is that Jojo will get a notification depending on how she has her GitHub set up, she'll probably get an email. It also appears when you just go to github.com on that main screen and the notifications. But mentioning somebody is a good way of making sure that they become aware through a notifications interface of what is happening with the project and perhaps what else they need to be working on. So let's see, in projects, okay, so I have the project already assigned here so that's great. And I'm going to go ahead and submit this new issue. One more thing you may want to do is notice that once I entered this issue, this is now issue number three, I can go ahead and add the status. So we'll put this as in progress since we're kind of working on it right now. And let's see if it's already showing up here, we may have to refresh the page. No, I didn't even have to do that. Look, it just showed up already in here and it's tagged it as in progress. All the other things have been added. Let's go ahead and add a due date. So sometimes you do have to go between the issues and the projects 'cause they have different fields. So in here I'm going to take care of this pretty quickly. So this will be part of sprint one and also be due just by tomorrow. We're going to work this pretty quick. I'm going to wait for Jojo to reply to this and I'll see what license she thinks might be good for our project. So let's check on this item right now, it looks like Jojo already replied and she thinks that we should use an MIT license, so that's great. I know how to do that. I'll just go ahead and take care of this right now. So I'm going to go over to my repository and go to the code section here. And I'm going to add a file, create a new file here, and I'm going to type in license. Notice that when I do that, if you are doing certain types of things in GitHub, it's actually going to give you this little template help. And it has one for when you create licenses which is really cool because it helps you pick a license. Let's go ahead and hit okay, just ignore the fact that it adds that because it's actually sending you to the insights for the project. Sort of a weird place for this to be, but it is what I need. So I'm going to say MIT license which is the one that we picked. It gives you a lot of information about the different licenses and what they're good for. It also gives you a way to add your name as well as the year. So we'll go ahead and hit review and submit. Here's the license, all prepared for me, ready to be added as a new file. And I'll go ahead and commit these changes, create a license. I'll go ahead and commit this to the main branch and say commit changes. And now let's go back to the code and we should see this license here. Now that means our little task is now done. So I can go to projects and actually I have it on another tab, but that's another good way. You can go to GitHub projects here and go directly to this. And I'll say, "Thanks Jojo, you are the best. I added the license file." Since this is kind of done, I'll go ahead and mark it as closed with this comment so I can add the comment, but I'm just going to go ahead and close this issue because it's done with the comment. And now let's go ahead and back out of here. You can see that the issue was automatically closed here and I'm going to hit the back button a few times to go back into my repo. So now that also has modified the issues. It's really nice. You can see that between what you can do in the projects and what's happening in the issues are all synced up automatically by GitHub which makes taking care of things really intuitive. Honestly, most of the software in the world is created with GitHub, so you can see that things that developers have had to use for a long time are really well thought out in GitHub projects.