Skip to content

Latest commit

 

History

History
21 lines (12 loc) · 780 Bytes

how-to-handle-github-issues.md

File metadata and controls

21 lines (12 loc) · 780 Bytes

How to handle Github issues

(This document is targeted mainly to Sharetribe team, but it's also good information for anyone who is about to file a new Issue report)

Does the report contain enough information to reproduce the issue?

  • Yes: Try to reproduce it.
  • No: Add a label more information needed and ask more info.

Can you reproduce the issue?

  • Yes: Add a label bug.
  • No: Close the issue, unless you feel this does needs further investigation. Leave the issue open and ask for further feedback from others, if so.

Is there an Issue with label more information needed and the issue reporter hasn't answered in two weeks?

  • Yes: Close the issue as inactive

Is there an Issue with a label "bug" and you know how to fix it?

  • Yes: Do it!