Essential storage keeps sign-in and learning features working. Google Analytics measures visits; Microsoft Clarity records interactions to help us improve usability. Both are optional and stay off until you choose. Read our privacy policy.
Create a repository, inspect each state transition, and stage exact files so the proposed snapshot is reviewable.
Change the last unpublished commit, restore files, and use mixed, soft, and hard reset only when you can name the risk.
Undo a published change with revert, keep shared history intact, and reserve rewrite commands for commits nobody else has.
Park incomplete changes, switch context without losing work, and know when a second worktree is clearer than a stash.
Mark releases with tags, distinguish lightweight pointers from annotated records, and treat published version tags as immutable.
Distinguish copies, backups, and a snapshot graph so later Git commands have a model instead of a memorized recipe.
Separate the local Git engine from GitHub hosting, issues, pull requests, and Actions so you know which layer owns each job.
Trace a change through the working tree, the index, and Git objects so status and add stop feeling like magic.
Install Git on Windows, macOS, or Linux, configure your identity and default branch, connect securely to GitHub, and push your first repository without guessing.
Learn Git version control and GitHub collaboration: repositories, commits, branches, merging, remotes, pull requests, issues, and workflow, with projects.
Add a workflow that runs on pull requests, fails on a real defect, and reports a result reviewers can trust.
Choose a transport, store credentials safely, and recover from auth failures without pasting tokens into the repository.
Stop accidental pushes to the default branch and require review or checks before history can move.
Give and receive review that talks about behavior and risk, then merge with a strategy you can justify.
Give issues and pull requests a repeatable shape so the team does not reinvent the same missing context.
Read a contributing guide, fork or branch correctly, keep a small diff, and respond to review without rewriting shared history.
Clone, fork, and add upstream remotes so your copy can receive updates without overwriting someone else's default branch.
Open issues that describe a problem, expected result, and reproduction steps instead of dumping a vague complaint.
Publish a versioned release from a tag and understand when Pages is a static site host rather than a substitute for Git.
Open a pull request with a clear change set, description, and linked issue so review can start from evidence.