Pulling from a Git remote

Note: This the fourth video in the Git for beginners series. Watch the first video here .

When you make a change to a local repository, you can push a change to a Git remote. Likewise, when the remote gets changed, you can pull the changes back to your local repository.

Today, you'll learn how to do the pull from the remote back to your repository.

Making a change to the remote

Usually, a change to the remote is made by another person who's working on the same project. They change the code on their computer, and they push it to the remote repository.

Once the remote repository changes, you can pull it back to your local repository to get the updated version.

That's the standard workflow.

But, since I'm working on the project alone, I'm going to show you how to change the remote repository directly on Github. Once we're done, we'll pull from there.

Changing the Github repository directly

Let's say we want to change the README.md text.

To do so, you can click on the pencil icon beside the Readme file. This brings you to an editor where you can change the text.

Pulling from a Git remote
Pulling from a Git remote
Github's editor

Once you're done. Scroll down to the bottom and write a commit message. You can click on the green button to commit the changes directly on Github.

Pulling from a Git remote
Pulling from a Git remote
Committing the changes

The project will be updated.

Fetching changes

Fork and other Git clients can show you the changes to a remote repository. They do it through a command called Git Fetch.

You can do a Fetch yourself by clicking on the empty arrow that points downwards. It's the leftmost arrow button on the top left-hand corner

Pulling from a Git remote
Pulling from a Git remote
The fetch button

Fetch checks the remote repository for any changes. It's like an email client that says you have three emails to read.

Once the Fetch is completed, you can see in the Git history that origin/master is on the update README.md commit, and the update README.md commit is one commit ahead of our local master branch.

Pulling from a Git remote
Pulling from a Git remote
origin/master tag is one commit ahead of the master tag.

On the sidebar, you can see the number 1 beside our master branch, and an arrow that points downwards. This tells us our branch is one commit behind the remote.

Pulling from a Git remote
Pulling from a Git remote
The master branch on the side tells us the same information—our master branch is one commit behind the remote.

Pulling changes

To update your local branch, you can click on the pull button. The pull button is the filled downwards arrow at the top left-hand corner. It's the one between Fetch and Push.

Pulling from a Git remote
Pulling from a Git remote
The pull button

When you click on Pull, you'll be able to select the branch you want to pull. Since we have tracked it previously, you can pull the master branch directly by clicking pull again.

Pulling from a Git remote
Pulling from a Git remote
Click on pull again to pull changes

When you pull the branch from the remote to your local repository, you'll see that master moves up to the same commit as origin/master .

Pulling from a Git remote
Pulling from a Git remote
master and origin/master are on the same commit again.

Wrapping up

Fetch checks if there are any changes in the remote repository.

Pull brings the changes from the remote repository to your local repository.

Thanks for reading. This article was originally posted on my blog . Sign up for my newsletter if you want more articles to help you become a better frontend developer.