Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upchore(repo): Create issue template #157
Conversation
I made this bespoke, but reviewers please let me know if you're aware of any prior art that you want to just adapt.
coveralls
commented
Aug 22, 2018
•
| @@ -0,0 +1,29 @@ | |||
| Thanks for filing in issue! Are you proposing an enhancement or reporting a bug? | |||
This comment has been minimized.
This comment has been minimized.
tylerbrandt
Aug 22, 2018
Contributor
We should separate instructions from the content we want them to provide (GitHub supports <!-- comments --> for the former; see e.g. https://raw.githubusercontent.com/mishoo/UglifyJS2/master/.github/ISSUE_TEMPLATE.md; that way you don't have to delete a bunch of stuff.).
|
|
||
| Any other relevant tools (like module bundlers, transpilers, etc.): | ||
|
|
||
| ## Expected behavior |
This comment has been minimized.
This comment has been minimized.
tylerbrandt
Aug 22, 2018
Contributor
I like the three-part guide of "What were you trying to do?" (may help resolve X/Y problem issues), "What did you expect to happen?", "What actually happened?" I encountered something like this scheme recently when reporting an issue with npm and it was helpful.
|
Sorry I missed this PR before. Thanks for this. We do no yet a standard set but this seems like a good start. Please merge the latest master in. |
spencerwilson-optimizely commentedAug 22, 2018
I made this bespoke, but reviewers please let me know if you're aware of any prior art that you want to just adapt.
Is the
Issue = Enhancement | Bugtaxonomy comprehensive (for this SDK, at least)?