A PR has this status: "Blocked — branched off an outdated base and needs to be rebased."
What does "outdated base" mean and why does it block merging?
Outdated base — the branch has diverged from main:
Situation
Solution
Branch base is behind main
git rebase main or git merge main
Merge conflicts exist
Resolve conflicts, then push
Why it blocks: merge conflicts may exist; CI may not have tested the branch against current main. Key vocabulary: base branch, diverged branch, rebase to update, merge conflict resolution, behind main by N commits.
5 / 10
A team announces: "We're migrating from feature branch per developer to a shared feature branch per story."
Code Review Comment: 'This PR is merging into `develop` directly. Shouldn't you be using a feature branch first to isolate your changes?' What does this comment primarily highlight about the team's branching strategy?
This comment focuses on the practice of directly merging feature branches into `develop`. The core principle behind using feature branches – isolating changes to prevent conflicts and simplify review – isn't being followed. Direct merges bypass this safety net, increasing the risk of integration issues.
7 / 10
Slack Message from Sarah (Senior Developer): 'I'm getting frustrated with how many branches we have. It's a nightmare to keep track of which ones are ready for review!' Considering the context, what branching strategy might be contributing to this problem?
Sarah's frustration stems from a likely overabundance of long-lived branches – a common pitfall of GitFlow. Each branch represents a potentially divergent line of development, making it difficult to track and manage the overall state of the codebase. Frequent merging introduces complexity.
8 / 10
PR Description: 'This PR incorporates changes from the `hotfix/security-patch` branch. To ensure stability, we'll need to rebase this onto the latest `develop` before merging.' What is the primary reason for rebasing in this scenario?
Rebasing is used here to integrate changes from an older, potentially unstable branch (the `hotfix/security-patch`) into the current state of `develop`. The goal is to create a cleaner history by reapplying the commits from the hotfix onto the latest version of develop, avoiding merge commit clutter.
9 / 10
Standup Update from Mark (Junior Developer): 'I'm working on a new feature in my own branch. I'll need to create a pull request when it's ready.' What is the core benefit of allowing developers to work on feature branches independently?
The ability to work on feature branches independently enables parallel development and faster iteration cycles. Developers can contribute changes without disrupting others' work or waiting for long-lived integration processes. This speeds up the overall delivery process.
10 / 10
API Response (from a Git service): `{"status": "error", "message": "Branch 'feature/new-ui' does not exist."}`, This API response indicates what issue?
The error message 'Branch 'feature/new-ui' does not exist' signifies that the specified feature branch (`feature/new-ui`) either never existed or has been deleted. This usually happens when a developer attempts to work on a non-existent branch, highlighting a potential issue with branch management.
What does this Version Control Strategy Language exercise cover?
This exercise, "🔀 Git Branching Strategy Vocabulary", tests your understanding of version control strategy language vocabulary and phrasing through 10 multiple-choice questions drawn from real workplace scenarios.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 10 questions. Each one presents a realistic sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Who is this Version Control Strategy Language exercise for?
It's designed for IT professionals and learners who want to sound natural discussing version control strategy language topics in English — useful for meetings, documentation, interviews, and day-to-day communication with English-speaking teams.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more Version Control Strategy Language exercises?
Browse the full Version Control Strategy Language exercises hub for more practice, or explore other exercise categories covering vocabulary, grammar, interviews, and workplace communication.