Creating GitHub Repository1:24
We haven't even really gotten to that point yet. So to start, we'll use maybe something a little generic like Council, but maybe at some point we'll dedicate time to actually think about the branding of our open source project, which is really important. So let's create that. Now here, we can either create a brand new repository from scratch, or if we have an existing one, we can use this code here. And yeah, do know, you need a basic understanding of Git and GitHub here. This is not going to be a series where I teach you about GitHub, it's more about actually maintaining projects on GitHub. So if this is blurry to you at all, maybe take a break and watch some of the Git lessons at Lerikas. Anyways, if I switch over to this forum folder, this is the actual project that we built in the Let's Build a Forum with TDD series. Now, you'll notice that we already have Git running,
Reinitializing Git History2:04
this is the actual project that we built in the Let’s Build a Forum with TDD series. Now, you’ll notice that we already have Git running, but this was, again, for that series, and I actually want that series to be separate from this one and the actual project that we maintain going forward. So I’m actually going to strip it all and start from scratch. Okay, so let’s initialize Git. Let’s do a git status. And of course, here’s all of the files that we have. We’ll add everything to the staging area. Then I will commit with a message of initial form. All right, so let’s switch over to Chrome. We’ll copy that and paste it in here. All right, we should be all set to go. So if I give this a refresh, this is now live in real time.
Removing Unnecessary Files2:38
All right, so let's switch over to Chrome. We'll copy that and paste it in here. All right, we should be all set to go. So if I give this a refresh, this is now live in real time. The next step, though, is if we scroll down, the README we're using is still the default Laravel README that comes with that repository. But I also see a couple of things like notes. This was from the last series where we were brainstorming some basic ideas. Tags, yeah, that's an editor-specific file. So why don't we remove some of these things? If I switch back and open our forum within Visual Studio Code, you'll see here, if we scroll down, tags, you know what, that's not even relevant anymore. That's from an editor I no longer use. So if I do a git status, and by the way, from now on I have an alias called gs.
Explaining Git Aliases3:18
That's from an editor I no longer use. So if I do git status, and by the way, from now on I have an alias called gs. And in fact, if we read that, you'll see it translates over. So if you ever see me do gs, that's git status, and the same will be true for gl. It's just a fancy git log that I use. The standard one will be fine for your needs if you're working log. Anyways, if we have a git status, yet we've deleted tags, let's also delete the notes as well. Okay, git status, and we'll remove these. Great, let's comment with a message of remove unnecessary files. Okay, next, if we open up the readme, yeah, once again, this is the readme that ships with Laravel. In our case, this is something that we will flesh out as we work on it. So to get started, we'll say
Writing Project README4:02
Okay, next, if we open up the README, yeah, once again, this is the README that ships with Laravel. In our case, this is something that we will flesh out as we work on it. So to get started, we'll say console, this is an open source forum that was built and maintained at laracasts.com. And then I'll add a to-do here that we need to flesh this out with instructions and usage examples and FAQ and all that stuff. So anyways, we've updated that. I'll do a git status. Yep, let's add that and commit with git commit -m "add README". And we'll push that up to GitHub. So now if I switch back to Chrome, and if we give this a refresh, yeah, we got rid of those unnecessary files, and we have the beginnings of our README file. And actually, on that note, trust me, your README is a very important thing. It's where almost everyone who visits your GitHub repository will immediately scroll to. So this is something that you want to flesh out as best as you can. So in the next
