Getting Started with GitHub
2 h 55 m
Lab Overview
In this lab, you will take the role of a GitHub administrator for new GitHub repositories. You will learn how to create and manage repositories as well as how to perform all the functions of GitHub Flow using the website in additional to the command line Git tools.

Related Learning Path(s):
Using GitHub
  • Learn how to setup your environment for GitHub
  • Learn how to use VS Code to work with GitHub and markdown files
  • Understand how to setup a GitHub repository
  • Understand how to setup branches in GitHub
  • Understand how to create a project and file issues
  • Basic understanding of source control systems
In this exercise, you will login to your lab virtual machine. 
In this exercise, we will download and install Git onto the LABVM. Then, you will learn how to verify the installation completed successfully.
In this exercise, we will create a account.
In this exercise, we will install Visual Studio Code to use as our text editor for use with Git.
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. In this exercise, you will create your first GitHub repository.
In GitHub, you use issues to record and discuss ideas, enhancements, tasks, and bugs. Issues make collaboration easier by: - Replacing email for project discussions, ensuring everyone on the team has the complete story, both now and in the future. - Allowing you to cross-link to related issues and pull requests. - Creating a single, comprehensive record of how and why you made certain decisions. - Allowing you to easily pull the right people into a conversation with @ mentions and team mentions.
In this exercise, you will create your first GitHub issue.

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 master.
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 master branch while you were working on your branch, you could pull in those updates.
In this exercise, you will create your first branch.
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.
In this exercise, you will create your first commit.
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.
In this exercise, you will open your first pull request.
It’s time to bring your changes together – merging your readme-edits branch into the master branch.
In this exercise, you will merge your first pull request.
This exercise is going to use GitHub Pages to create a website.
In this exercise, you will learn how to: - Create a new repository - Work with your repository on your local machine - Convert your repository into a website - Host and share your website
This exercise uses the command line, so first be sure to have completed the first four exercises where you installed Git, configured Git defaults, and setup Visual Studio Code as the default editor.
Real-Time Lab
Not Registered?
Create Account
Already Registered?
What are Labs?

Labs provide a live environment to get hands-on experience using the same tools and services in the real world.

Learn More