GitHub is a repository hosting service. Think of it as the “cloud” for code. GitHub will host your source code projects in a variety of different programming languages and keep track of the various changes made to every iteration. It is able to do this by using git, a revision control system that runs in the command line interface. Take a look at this video to develop understanding:
#1: Have your code reviewed by the community
#2: GitHub is a repository to save your code online and manage versions
#3: Collaborate and track changes in your code across versions
#4: GitHub can integrate with common platforms such as Amazon and Google Cloud
1. Basic Understanding of GitHub
2. Create and use of a repository
3. Start and manage a new branch
4. Make changes to a file and push them to GitHub as commits
5. Open and merge a pull request
A repository is usually used to organize a single project. Repositories can contain folders and files, images, videos, spreadsheets, and data sets – anything your project needs. We recommend including a README, or a file with information about your project. GitHub makes it easy to add one at the same time you create your new repository. It also offers other common options such as a license file.
Your hello-world repository can be a place where you store ideas, resources, or even share and discuss things with others.
Click Create repository.
Branching is the way to work on different versions of a repository at one time.
By default your repository has one branch named
master which is considered to be the definitive branch. We use branches to experiment and make edits before committing them to
When you create a branch off the
master branch, you’re making a copy, or snapshot, of
master as it was at that point in time. If someone else made changes to the
masterbranch while you were working on your branch, you could pull in those updates.
This diagram shows:
feature(because we’re doing ‘feature work’ on this branch)
featuretakes before it’s merged into
Have you ever saved different versions of a file? Something like:
Branches accomplish similar goals in GitHub repositories.
Developers, writers, and designers use branches for keeping bug fixes and feature work separate from the
master (production) branch. When a change is ready, they merge their branch into
readme-edits, into the new branch text box.
Now you have two branches,
readme-edits. They look exactly the same, but not for long! Next we’ll add our changes to the new branch.
Bravo! Now, you’re on the code view for your
readme-edits branch, which is a copy of
master. Let’s make some edits.
On GitHub, saved changes are called commits. Each commit has an associated commit message, which is a description explaining why a particular change was made. Commit messages capture the history of your changes, so other contributors can understand what you’ve done and why.
These changes will be made to just the README file on your
readme-edits branch, so now this branch contains content that’s different from
Nice edits! Now that you have changes in a branch off of
master, you can open a pull request.
Pull Requests are the heart of collaboration on GitHub. When you open a pull request, you’re proposing your changes and requesting that someone review and pull in your contribution and merge them into their branch. Pull requests show diffs, or differences, of the content from both branches. The changes, additions, and subtractions are shown in green and red.
As soon as you make a commit, you can open a pull request and start a discussion, even before the code is finished.
By using GitHub’s @mention system in your pull request message, you can ask for feedback from specific people or teams, whether they’re down the hall or 10 time zones away.
You can even open pull requests in your own repository and merge them yourself. It’s a great way to learn the GitHub Flow before working on larger projects.
1. Click the Pull Request tab, then from the Pull Request page, click the green New pull requestbutton.
2. In the Example Comparisonsbox, select the branch you made,
readme-edits, to compare with
master (the original).
3. Look over your changes in the diffs on the Compare page, make sure they’re what you want to submit.
4. When you’re satisfied that these are the changes you want to submit, click the big green Create Pull Request button.
5. Give your pull request a title and write a brief description of your changes.
When you’re done with your message, click Create pull request!
In this final step, it’s time to bring your changes together – merging your
readme-editsbranch into the
For More in-depth knowledge you can refer the following video tutorials and references: