Stage one coherent change

Stage one coherent change — guided practice

Use diffs to separate saved, staged and working content.

Start with main at its one base commit. Edit Bring: one item to Bring: one small item in notice.txt and save.

1. 1. Read the difference

   Run git diff and identify the removed/added Bring line.

   git diff -- notice.txt

   You should see: The new line adds the word small.

   Review detects accidental edits before history records them.

2. 2. Stage precisely

   Stage only notice.txt, then inspect the staged diff.

   git add notice.txt
   git diff --staged

   You should see: The staged diff contains that one-line replacement.

   Naming one file prevents unrelated files from entering the commit.

3. 3. Test staged versus working

   Add a fourth line, Access: step-free entrance, and save without staging. Run both diffs.

   git diff --staged
   git diff

   You should see: Staged diff shows the Bring edit; ordinary diff shows the Access addition.

   Staging captures content at that moment, not every later edit.

4. 4. Complete the contribution

   Stage the updated notice and commit. Count history.

   git add notice.txt
   git commit -m "Clarify item size and entrance"
   git rev-list --count HEAD

   You should see: Both intended edits are saved; count is 2.

   One coherent commit explains the whole notice clarification.