|
| 1 | +name: 🐞 Bug or error report |
| 2 | +description: Report an anomaly or unexpected behavior with a feature from this repository. |
| 3 | +labels: ['Needs: Triage :mag:', 'type:bug-suspected'] |
| 4 | + |
| 5 | +body: |
| 6 | +- type: markdown |
| 7 | + attributes: |
| 8 | + value: | |
| 9 | + - [x] Bug |
| 10 | +
|
| 11 | + Thank you for reporting a bug! Use the sections below to submit a bug **only** if it's related to features in this repo. |
| 12 | +
|
| 13 | + - All bug reports are welcome - we want to fix them! |
| 14 | + - This repo is maintained by volunteers. Please be courteous and patient. 🙂 |
| 15 | + - Remember to include sufficient details and context. |
| 16 | + - If you have multiple questions, suggestions, or bugs, please submit them in separate issues. |
| 17 | + - We accept pull requests. If you know how to fix it - go ahead! |
| 18 | +
|
| 19 | +
|
| 20 | + Please provide the following details about the issue you encountered. *Issues that do not provide the information requested in this form will be flagged as **incomplete** & automatically closed.* |
| 21 | +
|
| 22 | +- type: input |
| 23 | + id: feature |
| 24 | + validations: |
| 25 | + required: true |
| 26 | + attributes: |
| 27 | + label: Sample |
| 28 | + description: | |
| 29 | + Which feature are you having troubles with? |
| 30 | +
|
| 31 | + Use the feature name or URL. We don't want to be spend all this time diagnosing issues about the wrong feature, do we? |
| 32 | +
|
| 33 | +- type: input |
| 34 | + id: authors |
| 35 | + validations: |
| 36 | + required: true |
| 37 | + attributes: |
| 38 | + label: Author(s) |
| 39 | + description: | |
| 40 | + Who wrote the feature? |
| 41 | +
|
| 42 | + Because of the way this repository is configured, features authors do not get a notification when you create an issue. |
| 43 | +
|
| 44 | + For the section above **@mention any author of the feature**. Authors' GitHub handle can be found on the main feature documentation page, under the "Solution" section. |
| 45 | +
|
| 46 | + Issues without an @mention will be closed automatically, as authors won't get notified. |
| 47 | +
|
| 48 | + **NOTE:** Don't @mention the repo maintainers, they already get notified. |
| 49 | +
|
| 50 | +- type: markdown |
| 51 | + attributes: |
| 52 | + value: | |
| 53 | + Provide a clear & concise description of what the bug is. |
| 54 | +
|
| 55 | + **Do not attach ZIP files** of your code or compiled projects - instead, please publish your code to a public GitHub repo & post a link to it. |
| 56 | +
|
| 57 | +- type: textarea |
| 58 | + id: what-happened |
| 59 | + attributes: |
| 60 | + label: What happened? |
| 61 | + description: Describe the observed behavior |
| 62 | + placeholder: Tell us what you see! |
| 63 | + validations: |
| 64 | + required: true |
| 65 | + |
| 66 | +- type: textarea |
| 67 | + id: steps |
| 68 | + attributes: |
| 69 | + label: Steps to reproduce |
| 70 | + description: How do you reproduce this? Please provide as much step-by-step detail as possible. |
| 71 | + value: | |
| 72 | + 1. |
| 73 | + 2. |
| 74 | + 3. |
| 75 | + validations: |
| 76 | + required: true |
| 77 | + |
| 78 | +- type: textarea |
| 79 | + id: expected |
| 80 | + attributes: |
| 81 | + label: Expected behavior |
| 82 | + description: What did you expect to happen when the reproduce steps are followed? |
| 83 | + placeholder: Tell us what you expected to see! |
| 84 | + validations: |
| 85 | + required: true |
0 commit comments