Git 105: remote, pull, push และ GitHubGit 105: remotes, pull, push, and GitHub

Git is local first, but collaboration needs a shared place.

That shared place is called a remote.

GitHub is one popular remote host. GitLab, Bitbucket, and private servers can also host Git repositories.

What origin means

When a repository has a remote, the default remote is often named origin.

Check remotes:

git remote -v

If nothing appears, your practice repository has no remote yet.

Two common starting paths

There are two common ways to start.

Path A: clone an existing remote

git clone <repository-url>
cd <repository-folder>

git clone downloads the repository and sets up the remote for you.

Path B: create locally, then add remote

git remote add origin <repository-url>
git branch -M main
git push -u origin main

Use this when you created the project on your computer first and then made an empty remote repository.

Pull before push

Before pushing shared work, check whether the remote has changes you do not have.

git pull

For a beginner, read git pull as:

Bring remote changes into my current branch.

If Git reports conflicts, pause. Do not guess through conflict resolution.

Push your branch

Push sends local commits to the remote:

git push

The first push of a new branch often needs:

git push -u origin docs-add-learning-goal

The -u connects your local branch to the remote branch so future git push and git pull can be shorter.

Where GitHub fits

After a branch is pushed to GitHub, you can open a pull request.

A pull request is not Git itself. It is GitHub's review workflow around Git branches and diffs.

Use it to:

• explain what changed
• ask for review
• show diffs in the browser
• run automated checks
• discuss before merge

This is why the class is Git 10x, not GitHub 10x. Git is the foundation. GitHub is one place where the foundation becomes team workflow.

Safer remote habits

Before push:

git status
git log --oneline --decorate -5
git diff origin/main...HEAD

Then ask:

• am I on the right branch?
• are these commits the ones I meant to share?
• did I accidentally commit secrets?
• is my branch based on recent remote work?

Avoid force push until you understand exactly why it is needed and who else may be affected.

Practice: remote map

For a real repository or a practice clone, fill this out:

Remote host:

Remote name:

Default branch:

Current branch:

Command to pull:

Command to push this branch:

Where review happens:

Next: Git 106 - use Git safely with AI agents.