Which command sequence is commonly used to stage changes, check status, and prepare for a commit?

Which command sequence is commonly used to stage changes, check status, and prepare for a commit?

• A. git add, git status, git commit
• B. git commit, git push, git status
• C. git status, git log, git push
• D. git fetch, git merge, git status

Answer: (A)

Moving changes from your working area into the staging area, then checking what’s staged, and finally recording those changes as a commit is the typical flow. First, you use the command to add or stage your changes, which prepares exactly what you want to include in the next snapshot. Next, you check the status to see which changes are staged versus unstaged and to confirm you’re about to commit what you expect. Finally, you commit the staged changes, creating a new snapshot in the repository along with your descriptive message. This sequence directly matches the idea of staging, inspecting, and preparing a commit. The other options skip one of these steps or mix in unrelated operations like fetching or merging, which doesn’t align with the intended workflow.