Exercise 1: Stage and Commit Visually — Possible Solution ==================================================================== STEPS ------------------------------ 1. In a folder that's already a git repository (an existing project, or one initialized with git init from the integrated terminal, Chapter 6), open any tracked file and make a small edit — add a line, change a word. 2. Save the file (Ctrl+S). 3. Open the Source Control panel with Ctrl+Shift+G. The edited file appears under "Changes," and the Activity Bar's Source Control icon (Chapter 1) now shows a badge with the number 1. 4. Hover over the file in the list — a "+" icon appears next to it. Click it. The file moves from "Changes" up into "Staged Changes," the exact visual equivalent of git add . 5. Click into the message box at the top of the panel (above the Staged Changes list) and type a short, descriptive commit message, e.g. "Update greeting text". 6. Click the checkmark icon above the message box (or press Ctrl+Enter). The Staged Changes list clears, and the Source Control badge disappears — the commit succeeded. WHY THIS WORKS AS AN ANSWER ------------------------------ Hovering to reveal the "+" icon rather than looking for a menu item reuses the chapter's own described interaction exactly — this is VS Code's visual replacement for typing git add, staging one specific file rather than everything at once. Writing a real commit message before clicking the checkmark matters for the same reason it matters on the command line (git1's own foundation) — the checkmark button is disabled/does nothing useful without one, since a commit fundamentally requires a message whether it's created via git commit -m "..." or through this panel. The badge disappearing after the commit confirms the underlying git state actually changed — per this chapter's own comparison-box, staging via "+" and committing via the checkmark produce the EXACT SAME repository state git add and git commit would, which is why running git log in the integrated terminal afterward would show this new commit exactly as if it had been made from the command line.