The Staging Area
Part of the Version Control section of Coddy's Terminal journey — lesson 9 of 58.
Git does not commit every change automatically. Instead, you explicitly choose which changes go into the next snapshot. This two-step workflow is built around the staging area.
Think of it as a clipboard for the next commit. A file moves through three states:
- Working directory: where you edit files normally.
- Staging area: changes you have marked for the next commit.
- Repository: the permanent history, after you commit.
The point of staging is control. You can edit ten files, but stage only the two related to one bug fix, commit those, and then stage and commit the rest separately. Each commit ends up focused on one logical change.
You move files into staging with git add, and from staging into the repository with git commit.
Challenge
BeginnerThe folder contains an untracked file app.txt. Initialize the repository, then run git status --short to confirm the file shows up as untracked.
Try it yourself
Test yourselfThis lesson includes a short quiz. Start the lesson to answer it and track your progress.
All lessons in Version Control
2Getting Started
Initialize A RepositoryThe .git FolderConfigure Your IdentityGit StatusRecap - First Repo8Merging
What Is A MergeFast-Forward MergeThree-Way MergeMerge ConflictsResolve A ConflictRecap - Merge Master11Feature Branch Project
Project OverviewInitialize Main
Work On A BranchUpdate Main In ParallelMerge The FeatureClean Up3Tracking Changes
The Staging AreaGit AddGit CommitModifying A Tracked FileGit LogRecap - First Commits6Recipe Site Project
Project OverviewInitialize And IgnoreFirst CommitAdd A Second RecipeInspect The History