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)

In Git, the way you record changes starts by preparing them, then reviewing what you’ve prepared, and finally creating the commit. First, you add the changes you want to include with the staging command. This moves those changes into the staging area, which is like a ready-to-commit snapshot. Next, you run a status check to see exactly what’s staged and what’s still not staged, so you know what will be included in the next commit. Finally, you create the commit from the staged changes, which records that snapshot in the repository history with a message you provide. This sequence—git add, git status, then git commit—follows the natural flow of selecting what to record, verifying it, and then saving it as a commit. The other sequences mix in pushing or looking at history or updating branches without first staging and reviewing changes, so they don’t align with the typical staging-to-commit workflow.

In Git, the way you record changes starts by preparing them, then reviewing what you’ve prepared, and finally creating the commit. First, you add the changes you want to include with the staging command. This moves those changes into the staging area, which is like a ready-to-commit snapshot. Next, you run a status check to see exactly what’s staged and what’s still not staged, so you know what will be included in the next commit. Finally, you create the commit from the staged changes, which records that snapshot in the repository history with a message you provide.

This sequence—git add, git status, then git commit—follows the natural flow of selecting what to record, verifying it, and then saving it as a commit. The other sequences mix in pushing or looking at history or updating branches without first staging and reviewing changes, so they don’t align with the typical staging-to-commit workflow.