What makes a good GitHub issue?
A clear title, the steps to reproduce, expected versus actual behaviour, environment details, and screenshots or logs. For features, state the problem and the outcome wanted, not only a solution.
Explain it simply
An issue is a complaint slip another person must act on without calling you. The better the slip, the faster the fix.
For a bug: a specific title ('Login button does nothing on Safari 17'), steps numbered 1, 2, 3, what you expected, what happened, browser or OS version, and a screenshot or error text. For a feature: the user problem, who has it, and how success looks. Use labels, an assignee and a milestone, and issue templates in .github/ISSUE_TEMPLATE to make this routine.
Example
Title: Cart total shows NaN when quantity is empty
Steps: 1. Add item 2. Clear quantity box 3. Open cart
Expected: Rs 0
Actual: NaN
Env: Chrome 130, Windows 11What to say in the interview
"A good issue has a specific title, reproduction steps, expected and actual results, environment details and evidence like logs or screenshots. Feature requests describe the problem first. Labels and templates keep the tracker organized."