-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue Triage instructions #748
Conversation
CONTRIBUTING.md
Outdated
|
||
### Responding to issues | ||
|
||
Issues that are tagged `question` or `requires-reproduction` are great places to help. If you can answer a question, it will help the asker as well as anyone searching. If an issue needs reproduction, you may be able to guide the reporter toward one, or even reproduce it yourself using the [technique above](https://github.com/storybooks/react-storybook/blob/master/CONTRIBUTING.md#reproductions). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yourself using the [technique above]
yourself using this [technique]
CONTRIBUTING.md
Outdated
|
||
Once you've helped out on a few issues, if you'd like triage access, you can help label issues, and respond to reporters. New issues should be labelled as one of `bug`, `enhancement`, `question` or `discussion`. | ||
|
||
If an issue is a `bug`, if it doesn't have a clear reproduction that you have personally confirmed, mark it `requires-reproduction` and ask the author to try and create a reproduction, or have a go yourself, if you can. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If an issue is a
bug
, if it doesn't
If an issue is a bug
, and doesn't
CONTRIBUTING.md
Outdated
|
||
Once you've helped out on a few issues, if you'd like triage access, you can help label issues, and respond to reporters. New issues should be labelled as one of `bug`, `enhancement`, `question` or `discussion`. | ||
|
||
If an issue is a `bug`, if it doesn't have a clear reproduction that you have personally confirmed, mark it `requires-reproduction` and ask the author to try and create a reproduction, or have a go yourself, if you can. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that you have personally confirmed
that has been confirmed
mark it
label it with
, if you can
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that has been confirmed
I think we either need to use a reproduced
label (that you add when you personally confirm something) or the person that marks something as a bug should label it requires-reproduction
if they haven't confirmed it themselves. It's easy for things to slip through the cracks and not get confirmed otherwise.
I like the requires-reproduction
label because helping people reproduce things is a good beginner task.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
requires-reproduction
is an actionable label so 👍
@ndelangen should we merge this? |
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 3f2505d. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 1 targetSent with 💌 from NxCloud. |
Not sure if this covers all the labels as a they are currently used but it seems like a good starting point.