Skip to content

Commit

Permalink
new issue template
Browse files Browse the repository at this point in the history
  • Loading branch information
broofa committed Apr 2, 2024
1 parent b4c1dee commit d0b5d6d
Show file tree
Hide file tree
Showing 2 changed files with 34 additions and 32 deletions.
32 changes: 0 additions & 32 deletions .github/ISSUE_TEMPLATE/bug_report.md

This file was deleted.

34 changes: 34 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report.yml
@@ -0,0 +1,34 @@
name: Bug report
description: '`mime` support'

body:
- type: checkboxes
attributes:
label: Idiot Checks™
options:
- label: This is NOT about a specific MIME type⬌extension. Concerns with specific MIME types should be addressed in [the `mime-db` project](https://github.com/jshttp/mime-db/issues). (Be sure to search the issues first. Odds are good your concern has already been reported.)
required: true
- label: The title (above) is descriptive and specific to my problem (i.e. search-engine friendly)
required: true
- label: I know what an "MRE" is and will provide one below. (Not sure what an MRE is? (Read this)[https://stackoverflow.com/help/minimal-reproducible-example])
required: true

- type: input
attributes:
label: MRE (link)
description: URL to an MRE demonstrating your problem. This should be a project on StackBlitz, Codepen, or maybe CodeSandbox. A github repo is also acceptable, but not ideal. If you need a starting point, here's (a forkable-project on StackBlitz)[https://stackblitz.com/edit/mime-sample-mre?file=index.js]
placeholder: E.g. https://stackblitz.com/edit/mime-sample-mre?file=index.js

- type: textarea
attributes:
label: MRE (supporting details)
description: Someone has opened your MRE link... now what?
value: |
Actual behavior: ...
Expected behavior: ...
- type: textarea
attributes:
label: 'Actually, Can I just tell you about my problem ...'
description: |
This is a trap. Putting anything here means you're doing it wrong and this issue will be closed without comment. 😈

0 comments on commit d0b5d6d

Please sign in to comment.