5 exercises — real Jira comments, Slack messages, and PR reviews require you to recognise which Git phrasal verb fits. The wrong choice reveals a gap in technical fluency.
Git phrasal verbs covered
check out a branch — switch working directory to that branch
roll back to a version — revert to a previous stable state
phase out a library — gradually discontinue over a defined period
pull in changes — incorporate upstream commits into your branch
merge into a branch — target your PR at a specific branch
0 / 5 completed
1 / 5
A Jira ticket comment reads:
"Before you start, make sure to ___ the hotfix/3.1.2 branch — it has the security patch that needs to be in your build."
Which phrasal verb correctly means "switch your working directory to that branch"?
"Check out" is the standard Git phrasal verb for switching to a branch (or commit, tag). It sets your working directory to match that snapshot of the code. Command: git checkout hotfix/3.1.2 (legacy) or git switch hotfix/3.1.2 (modern). You will hear this constantly in team communication: "check out my branch", "have you checked out the release branch?", "I checked out the tag and reproduced the bug". Note: "check out" also appears in everyday English (check out this article, check out the problem) — context makes the Git meaning clear. In modern Git (v2.23+), git switch replaces checkout for branches, but the phrasal verb "check out" remains the conversational term.
2 / 5
An incident Slack message reads:
"P1 alert: the new release is returning 503s on the checkout endpoint. ___ ___ v2.8.4 immediately while we investigate."
Which phrasal verb means "revert to the previous stable version"?
"Roll back" is the standard DevOps and Git phrasal verb for reverting to a previous version of a deployment, codebase, or configuration. It implies a deliberate, controlled reversal — not just "undoing" but restoring a known-good state. Usage: "roll back the deployment", "roll back to the last stable release", "trigger a rollback", "the rollback took 4 minutes". Related: revert in Git refers to creating a new commit that undoes a previous one (git revert) — different from "roll back" which typically refers to restoring a deployment. "Step back" and "rewind" are not used in this technical context. "Go back to" is intelligible but non-technical — native DevOps speakers use "roll back".
3 / 5
An architecture decision record (ADR) states:
"The pusher-js library will be ___ ___ in Q2 2026. All real-time features must migrate to native WebSocket before then."
Which phrasal verb means "gradually discontinued and removed"?
"Phase out" means to gradually discontinue something — stopping support, usage, or maintenance incrementally over a defined period, rather than removing it abruptly. It is the standard technical term for the end-of-life process of a library, API, feature, or system. Usage: "phase out the legacy API", "the v1 endpoint is being phased out", "the deprecation phase is complete; the library has been phased out". Related: deprecate (formally mark as discouraged but still working), sunset (informal synonym — "we're sunsetting this feature"). "Shut down" = stop immediately, used for services/servers. "Turn off" = stop, typically for switches/toggles. Neither implies the gradual scheduled process that "phase out" does.
4 / 5
A tech lead's comment on a PR says:
"Nice work. Before this merges, can you ___ the latest commits ___ main? There have been some changes to the auth module that could conflict."
Which phrasal verb means "incorporate recent upstream changes into your branch"?
"Pull in" means to incorporate or bring in changes from another source — in this context, from the remote main branch into your feature branch. It is the phrasal verb equivalent of "fetch and merge" or "rebase on top of". Command: git pull origin main (merge strategy) or git fetch origin && git rebase origin/main (rebase strategy). Usage: "pull in the latest changes", "can you pull in main?", "I pulled in your commits". Important: "pull in" in Git is slightly different from "pull" alone — "pull in" emphasises bringing something into your current context, making the directionality explicit. "Copy from", "download from", and "grab from" are not used as technical Git phrasal verbs by native speakers.
5 / 5
A code owner comment on GitHub reads:
"This is ready to merge once CI passes. Please ___ it ___ release/4.0 — not main. We're building the release candidate and direct commits to main are frozen."
Which phrasal verb correctly describes targeting the PR to a specific branch?
"Merge into" is the standard verb + preposition combination for incorporating changes from one branch into another. On GitHub/GitLab/Bitbucket, this is the formal action: you merge a PR into a target branch. The directionality matters: you merge your branch into the target. Usage: "merge this PR into release/4.0", "merge feature branch into develop", "after review, merge into main". Related Git commands: git merge feature-branch (from the target branch), git checkout main && git merge feature/x. "Push into" is sometimes used colloquially but "merge into" is the precise technical term for Git PRs. "Branch into" is not used.