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 / 10 completed
1 / 10
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 / 10
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 / 10
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 / 10
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 / 10
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.
6 / 10
Code Review Comment: 'Okay, before you push this to the main branch, could you git checkout the 'feature/new-ui' branch? It contains the latest design updates.' Which phrasal verb best describes the action required here?
The phrase 'switch your working directory' is key here. git checkout specifically instructs you to change which branch you're working on. Options A and B relate to merging or committing, while rebase involves rewriting the history – a different operation entirely. This question tests understanding of branching workflows.
7 / 10
Slack Message: 'We're seeing intermittent errors in production after deploying the latest microservice. I've told Devops to git revert the last commit on the staging branch – it was causing a conflict.' What does git revert mean?
The core meaning is to undo a change. git revert specifically creates a new commit that negates the effect of a previously committed change. Options A and B relate to pushing or committing, while merging combines branches – a different action altogether. This clarifies a common mistake: confusing `revert` with `merge`.
8 / 10
PR Description: 'To ensure stability during the rollout, please git fetch origin and git merge origin/main before submitting this pull request. It's crucial to incorporate any recent changes.' What does git fetch origin accomplish?
git fetch origin downloads the latest updates from the 'origin' remote repository *without* automatically merging them. It's a preparatory step before you can then merge. Options A, B, and C all describe different operations on repositories; this question tests knowledge of the separate steps involved in updating your local branch.
9 / 10
Standup Update: 'I'm currently working on resolving a build failure. I need to git stash my changes temporarily to avoid conflicts while I investigate the root cause.' What does git stash do?
The key is understanding that `git stash` temporarily saves your uncommitted changes. It's like putting them on hold to work on something else without losing your progress. Options A, B, and C all represent different Git operations with distinct purposes. This highlights the use of stashing for temporary changes.
10 / 10
Code Owner Comment: 'Before merging, please git cherry-pick the latest hotfix commits from branch 'hotfix-security' into our development branch. We need to apply those fixes immediately.' What does git cherry-pick accomplish?
git cherry-pick allows you to select specific commits from one branch and apply them to another. It's not about merging entire branches; it's about selectively applying individual commits. Options A and C describe different merge or commit operations, while stashing is a separate function for holding changes.
What will I practise in "Git Commands: Fill in the Phrasal Verb"?
This module focuses on Phrasal Verbs — real workplace phrasing you'll use on the job. It contains 10 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 10 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Phrasal Verbs exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around phrasal verbs — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Phrasal Verbs exercises?
See the Phrasal Verbs hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.