GitHub basics

Lessons in this group, roughly in build order:

• creating-a-github-account-and-repository — The first concrete step on GitHub: register an account, then create a remote repository that hosts your…
• readme-license-and-repository-structure — The conventional top-level files GitHub recognizes — README, LICENSE, and a set of community health files…
• forking-a-repository — A fork is a server-side copy of someone else’s repository under your account, linked to the original — the…
• cloning-vs-forking — Two operations that are constantly confused: cloning copies a repo to your local machine; forking copies…
• github-issues — Issues are GitHub’s built-in tracker for bugs, features, and tasks — threaded discussions tied to a repo,…
• pull-requests — A pull request (PR) proposes merging one branch into another, wrapping the diff in a reviewable thread…
• code-review-and-comments — The review layer on a PR: inline line comments, batched reviews with a verdict, and suggested edits — the…
• merging-prs-merge-squash-rebase — The three ways GitHub can land a PR into the base branch — merge commit, squash, and rebase — each…