How do you stage changes and check status in Git?

• A. Use git add to stage and git status to check status.
• B. Use git commit to stage and git log to check status.
• C. Use git stage to stage and git display to check status.
• D. Use git push to stage and git status to check.

Answer: (A)

Staging changes and checking status are about preparing what you want to commit and seeing where your files stand in relation to the last commit. The right approach is to use a command that moves changes into the staging area, and a command that shows you what’s currently staged, unstaged, or untracked.

Use a command to stage, then a command to check status. Staging updates the index with the current content of your files, marking those changes as ready to be saved in the next commit. Checking status reveals three areas: changes that are staged for the next commit, changes that have been made but aren’t yet staged, and any new files not yet tracked by Git. This combination gives you a clear snapshot of what will be included when you later run the commit.

Other options don’t fit because they perform different actions: committing records the staged changes into the repository, not the act of staging; viewing the log shows past commits, not the current working tree or staging area; pushing sends commits to a remote, not staging or status; and there aren’t standard commands like stage or display in Git.