In Git, files move through three main areas: working directory, staging area, and repository. Which command moves changes from the working directory to the staging area?
Think about the command that prepares files for the next commit.
The git add command moves changes from the working directory to the staging area, preparing them to be committed.
What is the effect of running git commit -m 'message' after staging files?
Consider what happens after files are staged and you want to save a snapshot.
git commit takes the staged changes and saves them permanently in the local repository.
Which sequence of commands correctly moves a new file from creation to being saved in the local repository?
Remember the order: stage, commit, then push.
The correct order is git add to stage, git commit to save locally, then git push to send to remote.
You modified a file but after running git commit -m 'update', the changes are not saved in the repository. What is the most likely reason?
Think about what prepares changes for commit.
If changes are not staged with git add, git commit will not include them.
Which command guarantees that your staged changes are saved permanently in your local Git repository?
Consider which command creates a snapshot in your local repository.
git commit saves staged changes permanently in the local repository. git add only stages, git push sends to remote, and git status shows status.