Skip to content

chore(repo): Create issue template #157

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

Merged
merged 3 commits into from
Dec 26, 2018
Merged

chore(repo): Create issue template #157

merged 3 commits into from
Dec 26, 2018

Conversation

spencerwilson-optimizely
Copy link
Contributor

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 | Bug taxonomy comprehensive (for this SDK, at least)?

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
Copy link

coveralls commented Aug 22, 2018

Coverage Status

Coverage remained the same at 97.239% when pulling 6bb80e2 on sw/issue-template into 3ea6be2 on master.

@@ -0,0 +1,29 @@
Thanks for filing in issue! Are you proposing an enhancement or reporting a bug?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Contributor

@mikeproeng37 mikeproeng37 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@mikeproeng37 mikeproeng37 merged commit fb0cd7a into master Dec 26, 2018
@mikeproeng37 mikeproeng37 deleted the sw/issue-template branch January 14, 2019 21:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants