Practice English vocabulary for GitHub issue discussions: reproducing bugs, linking related issues, claiming issues, closing as won't fix, and locking inactive threads.
0 / 5 completed
1 / 5
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 / 5
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 / 5
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 / 5
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 / 5
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.