Work with remotes, fetch, pull and push

A remote is simply another Git repository that your local repository knows by a short name such as origin. GitHub can host a remote, but the remote concept belongs to Git itself.

git fetch origin downloads objects and updates remote-tracking references such as origin/main; it does not automatically merge them into your checked-out branch.

git pull is a convenience operation that fetches and then integrates according to configuration/options. git push sends local objects and asks the remote to update a reference. A push can be rejected when the remote branch has commits your local branch does not contain.

Run this in a disposable practice repository unless the lesson explicitly says otherwise.

git remote -v
git fetch origin
git log --oneline --graph --decorate --all
git pull --ff-only
git push origin main

Fetching first lets you inspect remote changes before integrating them. --ff-only makes pull refuse rather than create a merge when the update is not a fast-forward.

Your task: Using two clones of a disposable repository, commit from clone A and push. In clone B, run fetch and inspect origin/main before changing local main.

Avoid reflexively using force push. If rewriting a branch is intentional and agreed, --force-with-lease is usually safer than unconditional --force because it checks the remote state you expect.

Work with remotes, fetch, pull and push is complete when you can explain the state being changed before you run the command, not merely repeat the syntax.

Read further: official supporting documentation.