Git and GitHub Tutorial: Local Commits and Hosted Collaboration

Git maintains version history; GitHub adds a shared repository and collaboration features around that history. This tutorial follows a change from local editing to publication and review. You will distinguish the branch on your machine from its remote counterpart, understand what pushing transfers and connect a pull request to the commits it proposes. The distinction clarifies why a saved local change is not automatically visible to teammates.

Here's a popular Git and GitHub video — watch it, then summarize it with one click. Or paste any other YouTube link below.

— or paste your own YouTube link —

Want to keep the key points from a YouTube video? Paste the link below to turn it into structured notes.

Why Use Git and GitHub Tutorial: Local Commits and Hosted Collaboration

Frequently Asked Questions

How are Git and GitHub different?

Git is the version-control system that records and manipulates repository history. GitHub hosts repositories and provides review and collaboration tools. Using one does not make every operation part of the other.

Why does my local commit not appear on GitHub?

A commit initially exists in the local repository where it was created. It appears in the hosted repository after an appropriate push succeeds. Confirm the destination and branch when checking publication.

What does cloning a GitHub repository provide?

Cloning creates a local repository with the available history and a remote configuration pointing to the source. It normally also checks out files, giving you a place to inspect and develop changes.

Is a pull request the same as a push?

A push transfers objects and updates permitted remote references. A pull request opens a hosted discussion about integrating changes. Publishing a branch can support a pull request without immediately merging it.

Why check the remote URL?

The remote URL identifies where repository operations are directed. A project can have several remotes, including a personal fork and an upstream source. Checking that address prevents confusion about where commits were published.