GitHub/storybook
1
0
Fork 0
mirror of https://github.com/storybookjs/storybook.git synced 2025-03-20 05:02:37 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update to reflect labels in use

Browse Source
This commit is contained in:
Tom Coleman 2017-04-10 14:06:07 +10:00 committed by GitHub
parent 9191551038
commit 3629275142
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
CONTRIBUTING.md
View File

@ -58,25 +58,25 @@ If you are looking for a way to help the project, triaging issues is a great pla
### 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 [this technique](https://github.com/storybooks/react-storybook/blob/master/CONTRIBUTING.md#reproductions).
Issues that are tagged `question / support` or `needs 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 [this technique](https://github.com/storybooks/react-storybook/blob/master/CONTRIBUTING.md#reproductions).
### Triaging issues
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`.
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`, `new feature`, `question / support` or `discussion`.
If an issue is a `bug`, and it doesn't have a clear reproduction that you have personally confirmed, label it `requires-reproduction` and ask the author to try and create a reproduction, or have a go yourself.
If an issue is a `bug`, and it doesn't have a clear reproduction that you have personally confirmed, label it `needs reproduction` and ask the author to try and create a reproduction, or have a go yourself.
### Closing issues
- Duplicate issues should be closed with a link to the original.
- Unreproducible issues should be closed if it's not possible to reproduce them (if the reporter drops off line, it is reasonable to wait 2 weeks before closing).
- Unreproducible issues should be closed if it's not possible to reproduce them (if the reporter drops offline, it is reasonable to wait 2 weeks before closing).
- `bug`s should be closed when the issue is fixed and merged to `master`
- `enhancement`s should be closed when merged or if the feature is deemed to be not appropriate.
- `new feature`s should be closed when merged or if the feature is deemed to be not appropriate.
- `question`s should be closed when the question has been answered. If the questioner drops off line, a reasonable period to wait is two weeks.
- `question / support`s should be closed when the question has been answered. If the questioner drops offline, a reasonable period to wait is two weeks.
- `discussion`s should be closed at a maintainer's discretion.