GitHub Fundamentals

1. Introduction to GitHub

Learn the basics of GitHub, including understanding what GitHub is and how remote repositories work. Create your own GitHub account, set up and manage repositories, clone remote repositories to your local machine, and push changes to keep your projects updated and synchronized.

Remote Repositories

What is Github?

Creating a GitHub Account

Creating a Repository

Cloning a Remote Repository

Pushing Changes

Introduction Summary Quiz

2. Basic Interaction with Remotes

Master the fundamentals of interacting with remote repositories by learning how to work with remote branches, fetch and merge remote changes, and pull updates from remote repositories. This section will equip you with the essential skills to manage and synchronize your work with remote teams effectively.

Information about Remotes

Remote Branches

Simulating Collaboration

Fetching and Merging Remote Changes

Creating a New Branch Remotely

Pulling Changes

Remotes Summary Quiz

3. More Advanced Workflows

Delve into advanced Git workflows by mastering the techniques of pulling and pushing changes, pushing local branches, and rebasing changes. This section will help you refine your version control skills, enabling you to handle more complex development scenarios and maintain a clean, efficient project history.

Making Local and Remote Changes

Syncing the Repositories

Pushing Local Branches

Rebasing Basics

Performing a Rebase Operation

Commands Cheatsheet

Final Quiz

Pulling Changes

As a matter of fact, fetching and then immediately merging changes is an extremely common scenario. That's why Git provides a single command, git pull, that combines these two operations and integrates the changes into the current branch.

Let's now pull the remote changes made by John into our local repository:

As you can see, the output of this command is basically a combination of the outputs of the git fetch and git merge commands.

In case there were also changes on the remote main branch not merged with john/test, a fast-forward merge would be performed into the local main branch (provided that there were no conflicts).

You can also run the git remote show origin command to see that there is indeed a remote john/test branch, but our local repository doesn't have the corresponding local branch.

Let's create a local branch for it by running the git checkout command:

Let's break down what has just happened:

We switched to the john/test branch;
Git automatically copied the remote branch's contents into the local branch;
The working tree has been updated to reflect the contents of the john/test branch.

We can easily verify that we are on this branch and that it is up-to-date with its remote counterpart by looking at the latest commit:

The -n flag specifies the number of commits to display. In this example, -n 1 tells Git to show only the most recent commit.

Everything was clear?

Section 2. Chapter 6

Course Content

GitHub Fundamentals

Pulling Changes

Let's now pull the remote changes made by John into our local repository:

As you can see, the output of this command is basically a combination of the outputs of the git fetch and git merge commands.

You can also run the git remote show origin command to see that there is indeed a remote john/test branch, but our local repository doesn't have the corresponding local branch.

Let's create a local branch for it by running the git checkout command:

Let's break down what has just happened:

We switched to the john/test branch;
Git automatically copied the remote branch's contents into the local branch;
The working tree has been updated to reflect the contents of the john/test branch.

We can easily verify that we are on this branch and that it is up-to-date with its remote counterpart by looking at the latest commit:

The -n flag specifies the number of commits to display. In this example, -n 1 tells Git to show only the most recent commit.

Everything was clear?

Section 2. Chapter 6