During a code review of a recent pull request for the `authentication` module, Sarah notices that a particular line of code has been modified by three different contributors over several weeks. The reviewer, Mark, wants to understand the history of this change to assess its impact and potential conflicts. Which command would be MOST helpful for Mark to investigate this situation within the project's Git repository?
The correct answer is `git blame -L ,`. While other commands like `git diff` and `git log` are useful in Git workflows, `git blame` specifically focuses on tracking the history of changes to individual lines of code. This is essential for understanding why a particular piece of code exists and who modified it, which is exactly what Mark needs when assessing the impact of a change during a code review. The other options focus on broader commit histories rather than line-level modifications.
7 / 14
git blame -L ,
During a code review of a recent pull request for the `authentication` module, Sarah notices that a particular line of code has been modified by three different contributors over several weeks. The reviewer, Mark, wants to understand the history of this change to assess its impact and potential conflicts. Which command would be MOST helpful for Mark to investigate this situation within the project's Git repository?
The correct answer is `git blame -L ,`. While other commands like `git diff` and `git log` are useful in Git workflows, `git blame` specifically focuses on tracking the history of changes to individual lines of code. This is essential for understanding why a particular piece of code exists and who modified it, which is exactly what Mark needs when assessing the impact of a change during a code review. The other options focus on broader commit histories rather than line-level modifications.
8 / 14
git blame -L ,
During a code review of a recent pull request for the `authentication` module, Sarah notices that a particular line of code has been modified by three different contributors over several weeks. The reviewer, Mark, wants to understand the history of this change to assess its impact and potential conflicts. Which command would be MOST helpful for Mark to investigate this situation within the project's Git repository?
The correct answer is `git blame -L ,`. While other commands like `git diff` and `git log` are useful in Git workflows, `git blame` specifically focuses on tracking the history of changes to individual lines of code. This is essential for understanding why a particular piece of code exists and who modified it, which is exactly what Mark needs when assessing the impact of a change during a code review. The other options focus on broader commit histories rather than line-level modifications.
9 / 14
git blame -L ,
During a code review of a recent pull request for the `authentication` module, Sarah notices that a particular line of code has been modified by three different contributors over several weeks. The reviewer, Mark, wants to understand the history of this change to assess its impact and potential conflicts. Which command would be MOST helpful for Mark to investigate this situation within the project's Git repository?
The correct answer is `git blame -L ,`. While other commands like `git diff` and `git log` are useful in Git workflows, `git blame` specifically focuses on tracking the history of changes to individual lines of code. This is essential for understanding why a particular piece of code exists and who modified it, which is exactly what Mark needs when assessing the impact of a change during a code review. The other options focus on broader commit histories rather than line-level modifications.
10 / 14
John from the security team Slack channel sends the following message: "Hey @`dev_user`, just wanted to flag that this PR introduces a potential XSS vulnerability. Please review your input sanitization logic carefully.". What does the '@' symbol in this message signify?
The '@' symbol in Slack is used to *mention* a specific user. This alerts them directly within the channel and indicates they should review the message or related content (in this case, the PR). It's distinct from sending an email or inviting someone to join a different channel.
11 / 14
Maria is writing the description for a pull request that introduces a new feature. She writes: "This change adds support for OAuth 2.0 authentication using Google accounts. It utilizes the google-auth library and follows best practices for secure API key management. The changes are backwards compatible with version 1.2.". What does 'backwards compatible' mean in this context?
'Backwards compatible' signifies that the new changes do not negatively impact existing code. Version 1.2 of the project should continue to work as expected after this PR is integrated – a crucial concept in OSS maintenance and avoiding disruption.
12 / 14
David, a contributor, wants to propose a significant change to the project's core logging system. He submits a document titled 'RFC: Enhanced Logging Capabilities'. What is an RFC (Request For Comment) in the context of open source development?
An RFC is a formal mechanism within open-source communities for proposing new features, designs, or improvements. It's a discussion document used to gather feedback and ensure that any changes align with the community's goals before being implemented.
13 / 14
Emily discovers that a recent pull request introduces a breaking change to the project's public API. The PR description explicitly states: 'This change deprecates the legacy endpoint and requires clients to migrate to the new version'. What is the primary reason this is considered significant in an open-source project?
Breaking changes in an API represent incompatibilities. Users relying on the old endpoint will require modifications to their applications, representing a considerable effort and potential disruption – a key consideration when maintaining stability within an open-source project's ecosystem.
14 / 14
Ben submits a pull request to fix a bug in the project's core library. The PR is reviewed and marked as 'wontfix'. What does 'wontfix' typically mean in a code review context?
'Wontfix' indicates that the maintainers have assessed the issue and decided it isn't a priority for addressing. This often stems from factors like low impact, high effort to fix, or conflicting priorities within the project – a common outcome in managing an open-source codebase.
What does the "Open Source Community Vocabulary" exercise practise?
Practice OSS community vocabulary: contributor ladders, governance models, RFC process, and CNCF vocabulary.
How many questions are in this exercise?
This exercise has 14 questions, each multiple-choice with a full explanation shown after you answer.
What English level is this exercise for?
This exercise is tagged Intermediate. If the vocabulary feels difficult, browse the Conference & Community category page for an easier module to start with.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free with no account, sign-up, or paywall.
Do I get feedback if I answer incorrectly?
Yes — whichever option you choose, right or wrong, you'll immediately see an explanation clarifying the correct term and why the other options don't fit.
Can I retry this exercise?
Yes — once you finish all the questions, a "Try again" button on the results screen resets the exercise so you can practise as many times as you like.
Do I need an account to track my progress?
No account is required. Your progress bar and score for this session are tracked in the browser as you go, but nothing is saved once you leave the page.
Is "Open Source Community Vocabulary" part of a larger series?
Yes — it's one exercise in the Conference & Community category on CoderSlingo. See the category page for the full list of related exercises on similar terminology.
Can I link directly to this exercise?
Yes — this exercise has its own permanent URL, so you can bookmark it or share the link directly with a colleague or study partner.
Where can I find more exercises like this one?
See the Conference & Community category page for related exercises, or browse the main Exercises hub for other IT English topics.