1 / 5
You select which modified files go into the next commit. You ___ the changes.
-
-
-
-
Stage changes means adding them to the staging area (
git add) so they'll be in the next commit.
- stage changes / files — prepare them to be committed
- Then you commit the staged changes
"Queue up" and "park" are not Git terms. Example:
"Stage only the files you changed, then commit."
2 / 5
You record your staged changes into the local history with a message. You ___ the changes.
-
-
-
-
Commit changes means recording them in the local repository history.
- commit changes / a fix — with a commit message
- Then you push commits to the remote
"Submit" and "lodge" are not used in Git. Example:
"Commit your work with a clear message before you push."
3 / 5
Your local commits aren't on the server yet. To send them to the remote, you ___.
-
-
-
-
Push sends your local commits to the remote repository;
pull brings remote changes down.
- push commits / changes — to the remote
- pull — fetch and merge remote changes locally
"Upload up" and "flush" are wrong. Example:
"Push your branch so I can review it."
4 / 5
You rewrote shared history and must overwrite the remote branch. You ___ the branch (carefully!).
-
-
-
-
Force-push overwrites the remote branch with your local version, even when histories diverge.
- force-push (
git push --force, ideally --force-with-lease) - Risky on shared branches — it can erase others' commits
The other variants are not real terms. Example:
"After the rebase you'll need to force-push your feature branch."
5 / 5
Your last commit message had a typo. Without making a new commit, you ___ it.
-
-
-
-
Amend a commit means rewriting the most recent commit (its message or contents).
- amend a commit (
git commit --amend) - Different from revert, which creates a new commit that undoes a previous one
Note: amending already-pushed commits needs a force-push. Example:
"Just amend the commit to fix the typo in the message."