Add the GitHub issue template #668
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collecting all the relevant details early on means less back and forth between the poster and project contributors. Asking to create a small reproducible demo means less time wasted trying to repro the bug. Brunch has been doing this for a while and it has really helped. There are people who deleted the template and went free-form in their bug reports but for the most part, people have actually been filling that in: https://github.com/brunch/brunch/issues?q=is%3Aissue+is%3Aclosed A lesser percentage of the people were creating the demos, but a few definitely were. The details, and the demos especially, led to faster resolution times, which a win for everyone.
ghost
added
the
|
Thanks so much. I was meaning to do this but couldn’t find the time so I really appreciate you stepping up! |
|
Np!👌
|
feiqitian
pushed a commit
to feiqitian/create-react-app
that referenced
this pull request
Oct 25, 2016
Collecting all the relevant details early on means less back and forth between the poster and project contributors. Asking to create a small reproducible demo means less time wasted trying to repro the bug. Brunch has been doing this for a while and it has really helped. There are people who deleted the template and went free-form in their bug reports but for the most part, people have actually been filling that in: https://github.com/brunch/brunch/issues?q=is%3Aissue+is%3Aclosed A lesser percentage of the people were creating the demos, but a few definitely were. The details, and the demos especially, led to faster resolution times, which a win for everyone.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Collecting all the relevant details early on means less back and forth between the poster and project contributors. Asking to create a small reproducible demo means less time wasted trying to repro the bug.
Brunch has been doing this for a while and it has really helped. There are people who deleted the template and went free-form in their bug reports but for the most part, people have actually been filling that in:
https://github.com/brunch/brunch/issues?q=is%3Aissue+is%3Aclosed
A lesser percentage of the people were creating the demos, but a few definitely were. The details, and the demos especially, led to faster resolution times, which a win for everyone.
I do see bugs account for about 13% of issues so there might be a bit less value of this than for Brunch, but the first few bug reports I picked from the list have @gaearon asking for env details/demo, which is a routine work that can be precisely removed with the issue template.