Practice English vocabulary for GitHub issue discussions: reproducing bugs, linking related issues, claiming issues, closing as won't fix, and locking inactive threads.
0 / 10 completed
1 / 10
You have confirmed that the reported bug also happens on your system. What do you write in the issue?
'I can reproduce this' is the standard phrase for confirming a bug. Providing your OS and runtime version (macOS 14, Node 20) gives maintainers the information needed to investigate.
2 / 10
You believe the current bug is connected to a previously filed issue. How do you reference it?
'The issue is related to #1234' is the soft linking phrase. Use 'duplicate of #1234' only if the issues are identical. 'Related to' signals a connection without claiming they are the same.
3 / 10
You want to work on an open issue and need to check if another contributor has already claimed it. What do you ask?
'Is it available?' is the natural phrase for asking if a task is unassigned and open for someone to pick up. It is widely used in open-source contribution culture.
4 / 10
The maintainer has decided not to implement the requested feature and explains their reasoning before closing. Which phrase is the standard close reason?
'Won't fix' is the canonical GitHub close label and phrase for issues or feature requests the maintainer has intentionally decided not to address. GitHub also uses 'Not planned' as an official label.
5 / 10
The issue has had no replies or activity for a long time, so the maintainer disables further comments. Which phrase describes this?
'Locking the issue due to inactivity' means preventing new comments on an issue that has been idle for too long. GitHub's issue lock feature is commonly used to manage stale threads.
6 / 10
You're reviewing a pull request for a new feature. The developer has added a complex algorithm to the component and included extensive comments explaining each step. Which of the following best describes your initial reaction?
The goal of code reviews is to ensure clarity and maintainability. While extensive comments can be helpful, the core algorithm should ideally be straightforward. Option 2 reflects this – sufficient context for understanding *given* the implementation. Options 1 and 4 are too extreme; option 3 suggests a fundamental problem with the design.
7 / 10
A colleague posts in Slack: 'I'm struggling to understand how to integrate this API. The documentation is really unclear.' What's the most appropriate response you could offer?
The colleague is explicitly stating confusion. Offering immediate, unhelpful advice (option 1) or suggesting generic resources (option 2) doesn't address their need for support. Option 4 provides a collaborative approach – actively assisting with the documentation and explaining it together. Option 3 is too vague.
8 / 10
You're drafting the description for a pull request that implements a new user authentication flow. Which of the following phrases would be most effective in summarizing the changes?
A pull request description should clearly state *what* was changed. Option 2 provides specific details about the implemented functionality (login and registration with security). Options 1 and 3 are too vague and lack technical detail. Option 4 focuses on a bug fix rather than new feature implementation.
9 / 10
During a daily standup, Sarah says: 'I'm blocked on issue #123 because I need the database schema documentation.' What should you ask to help her proceed?
Sarah has identified a dependency – the database schema. Asking if she's already requested it is a logical next step to understand the current status and what actions are needed. Option 1 is unhelpful; option 3 encourages more information gathering; option 4 inappropriately takes over her task.
10 / 10
A maintainer closes an issue with the comment: 'Unable to reproduce. No further action.' What does this mean?
'Unable to reproduce' indicates that the team attempted to replicate the described problem but failed. This often means the reported issue was not actually present in their environment or the steps to reproduce were misunderstood. It's a standard closure reason when verification fails.
What will I practise in "Issue Discussion Vocabulary"?
This module focuses on Open Source Contribution — 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 Open Source Contribution exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around open source contribution — 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 Open Source Contribution exercises?
See the Open Source Contribution 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.