Understand Git: working files, staging, and commits
See how working files, the staging area, and committed history differ in a small Git repository.
Learn Git by doing
Small examples. Useful Git skills.
Understand what Git records, practice the everyday workflow, and solve the problems that interrupt real projects. Every lesson works with ordinary Git commands in a fresh local folder.
Start the beginner pathBuild your foundation
Create a Git repository and your first commit
Initialize a local repository, configure its author identity, and record a first commit without a hosting account.
Read Git status, diffs, and commit history
Identify staged, unstaged, and untracked changes and inspect the exact snapshot that a commit records.
Create Git branches and merge a feature
Practice a local feature branch and a deliberate merge, then understand the resulting commit graph.
Understand Git remotes: clone, fetch, pull, and push
Practice sharing commits with a local bare remote and two clones, without credentials or a hosting account.
A daily Git workflow: review, verify, commit, and sync
Practice a repeatable Git workflow that separates reviewing changes, checking behavior, and publishing commits.
Solve a Git problem
How to stage only part of a file in Git
Use git add --patch to stage one change while leaving another edit in the same file out of your commit.
Undo the last Git commit while keeping your changes
Use a soft reset to revise an unpublished last commit without losing its files or staged changes.
Undo a pushed Git commit with revert
Reverse a shared change with git revert while preserving the original commit and remote history.
Resolve a Git merge conflict step by step
Reproduce a text merge conflict, inspect both versions, write the intended result, and finish the merge.
Recover a lost Git commit using reflog
Find a recently displaced local commit in reflog and preserve it on a new recovery branch.
Use Git worktrees to work on two branches at once
Create a second checkout with git worktree, keep pending edits separate, and inspect both branches safely.
Already reviewing agent changes? Read the workflow guides. For GitGlow controls and edition requirements, use the product documentation.