Creating an account on GitHub
To complete this lesson, first, you need to create a free account on GitHub (or use an existing one). The profile is your public page on GitHub like in social networks. When you look for a job as a programmer, employers might view your GitHub profile and take it into account as they consider you for the job.
When you create an account, on Step 2: Choose your plan, and check Unlimited public repositories for free.
Other steps are typical for any website.
After you complete the registration, you will see a dashboard. At the top of the page, you will see the search box and information about your profile.
You can open your profile and make changes (for example, you can add a bio or set a picture).
Array.reverse()
To complete this lesson, first, you need to create a free account on GitHub (or use an existing one). The profile is your public page on GitHub like in social networks. When you look for a job as a programmer, employers might view your GitHub profile and take it into account as they consider you for the job.
When you create an account, on Step 2: Choose your plan, check Unlimited public repositories for free.
Other steps are typical for any website.
After you complete the registration, you will see a dashboard. At the top of the page, you will see the search box and information about your profile.
You can open your profile and make changes (for example, you can add a bio or set a picture).
To complete this lesson, first, you need to create a free account on GitHub (or use an existing one). The profile is your public page on GitHub like in social networks. When you look for a job as a programmer, employers might view your GitHub profile and take it into account as they consider you for the job.
When you create an account, on Step 2: Choose your plan, check Unlimited public repositories for free.
Other steps are typical for any website.
After you complete the registration, you will see a dashboard. At the top of the page, you will see the search box and information about your profile.
You can open your profile and make changes (for example, you can add a bio or set a picture).
Exploring a repository
GitHub hosts millions of projects written in different programming languages. Each project is placed in its own container called a repository (repo) that can store code, configurations, datasets, pictures, and other files included in your project. Any changes to files within a repo will be tracked via version control.
If you wish to find some specific repository of a project, type its name or a part of the name in the search box. You will see a list of suitable repositories.
Sometimes, the name of a repository can be too large or there are many repositories with the same name. For example, try searching for intro-to-github without hyperskill/.
Usually, you will have a link to a repository. Many open-source projects publish links on their personal websites, or your colleagues may give you a link to a project's repository.
Here is the direct link to our existing demo repository. Please, open this repo and look at its internal structure.
There are two files in the Code tab. README.md is a file that describes the project; every repository should include this file. GitHub finds this file and displays its content below the repo. The other file is .gitignore, which specifies which files and directories will be ignored by Git.
Although this repo is public, you cannot modify files in this repo directly, because you have read-only access to any public repository. To modify the files, you must be a collaborator of a project.
The Pull requests tab contains proposals to make changes in the files located in the repository (adding, deleting, or modifying files). The repo's owners can review a request and make your changes if they look good enough.
You can create an Issue or make a Pull request (PR) to contribute to the project, even if you are not a collaborator.
In our project, the Wiki tab is empty, but actually, it is a place for the project's documentation (how to use it, how it was designed, core principles, and so on). Whereas a README.md is intended to quickly let readers know what your project can do, wikis can be used to provide additional documentation.
The Projects tab is not discussed in this lesson.
In the Insight tab you can find stats and information about this repository.
You may also look at the commit(s) which represent changes of the repo's content. Here is a link to see it directly. We will learn more about commits further.
Explore
Here is the explore section