After staging the changes, the developer will ___ them with a descriptive message.
To commit changes means to record them as a snapshot in the repository history. Commit is the foundational Git term, behind "commit message" and git commit. Save up, lock in, and post out are informal or wrong. Developers "commit the changes with a clear message," so commit changes is the correct collocation.
2 / 5
To share the work, the developer will ___ the branch to the remote repository.
To push a branch means to upload local commits to a remote. Push is the precise term, behind git push. Send up, upload out, and post over are informal. Developers "push the branch to origin," so push the branch is the correct collocation.
3 / 5
To save half-finished work without committing, the developer can ___ the changes.
To stash changes means to temporarily shelve uncommitted work to get a clean working tree. Stash is the precise Git term, behind git stash. Hide up, park out, and pocket are informal or wrong. Developers "stash the changes before switching branches," so stash changes is the correct collocation.
4 / 5
When two branches change the same lines, Git reports a ___ that must be resolved.
A merge conflict occurs when Git cannot automatically reconcile divergent changes to the same lines. Merge conflict is the precise term, behind "resolve a conflict." Clash up, collision out, and mix over are not the standard phrase. Developers "resolve the merge conflict," so a merge conflict is the correct collocation.
5 / 5
To undo a bad commit that is already public, the safest option is to ___ it with a new commit.
To revert a commit means to create a new commit that undoes a previous one — safe for shared history. Revert is the precise Git term, behind git revert. Undo up, roll off, and cancel out are informal or wrong (and "reset" rewrites history, unsafe when public). Developers "revert the bad commit," so revert a commit is the correct collocation.