1. Setting up a repo
Now that we've solidified our GitHub knowledge, we'll learn how to set up a GitHub repo.
2. Create a new repository
We have two options that both lead us to the first step. In the profile view,
3. Create a new repository
we can either click the plus sign in the top-right
4. Create a new repository
to see the dropdown menu and select New repository,
5. Create a new repository
or, in our repositories view,
6. Create a new repository
we can click the green New button.
7. Create a new repository
Both take us to the Create a new repository page.
8. Create a new repository
Here, we can import a repo
9. Create a new repository
or use a template from a previous repo. As we are starting from scratch,
10. Create a new repository
we will take the third option to create a new repo.
11. Create a new repository
The first step is to name our repo. Our project will use data on soccer results from top-level men's teams in the UK, Italy, and Spain to look at goal trends. We'll name it soccer analysis. We can also include a short description of our project, which is helpful if we expect to collaborate with others.
12. Public repository
We have a few more decisions to make before we can create our repo. This will be an open project, so we will select the Public option. This means our project will be visible to anyone on the internet, but we can still control who can make changes to our projects.
13. Repository files
Nearly there! We need to initialize the repo with some files: a README file and a dot-gitignore file.
14. Repository files
It is standard practice for all repo's to include a README file, these act as a guide for the project and are helpful for collaboration as they provide details on what the project is about and how it can be used.
15. Repository files
We'll also add a dot-gitignore file. This is like the blocked phone numbers list on the phone. If we don't want someone to call us, we add their number to the block list! The gitignore file blocks or ignores specific files from being committed or saved into our repo. These files usually contain confidential information or are system files. GitHub offers several templates. We'll use Python.
16. Repository files
We'll also select None for the license, which means default copyright laws apply.
17. Repository files
We're ready to create our first public repo by hitting the big green button!
18. Navigating a repo
Here is a view of our new repo! We can see the README and dot-gitignore files are part of the project already.
19. Navigating a repo
We are in the Code section of the repo. This is where all the folders and files are visible.
20. Navigating a repo
Notice the About section on the right. This is the description we added when creating the repo.
21. Navigating a repo
We can also edit it by clicking on the icon that looks like a gear.
22. Navigating a repo
The following section is called Issues. Issues are where we track tasks or problems and also communicate with others. We don't have any issues at the moment.
23. Navigating a repo
The next section is called Pull Requests. Pull requests or PR for short, is a request to make a change to the project. Think of it like a suggestion box. A PR will show the suggested changes and compare them to the project's current version. We can view the suggestion and decide if we want to accept it. We don't have any PRs at the moment, either!
24. Navigating a repo
Before practicing, let's look at the Settings. Here we have various options to make changes to our repo, including changing the name and access permissions. We'll explore access options later on. For now, we only need to know where to find these settings.
25. Let's practice!
Let's try making a public repo!