A repository isthe basic unit of GitHub, most commonly a single project. Repositories cancontain folders and files, including images – anything your project needs.Because we recommend including a README, or a file describing the project, inevery repository

Branching is the way to work on different parts of arepository at one time.

On GitHub, savedchanges are called commits.Commits are pretty glorious, because a bunch of them together read like thehistory of your project.

Each commit has an associated commitmessage, which is a description explaining why a particularchange was made. Thanks to these messages, you and others can read throughcommits and understand what you’ve done and why.

Pull Requests are theheart of collaboration on GitHub. When you make a pull request, you’reproposing your changes and requesting that someone pull in your contribution -aka merge them into their branch. GitHub’s Pull Request feature allows you tocompare the content on two branches. The changes, additions and subtractions,are shown in green and red and called diffs (differences).

As soon as you make a change, you can open a Pull Request.People use Pull Requests to start a discussion about commits (code review) evenbefore the code is finished. This way you can get feedback as you go or helpwhen you’re stuck.

By using GitHub’s @mention system in your Pull Request message, you canask for feedback from specific people or teams, whether they’re down the hallor 10 time zones away.