chore: add issue forms #4617
Merged
chore: add issue forms #4617
Conversation
This file contains hidden or 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
Comment on lines
+60
to
+83
| - type: textarea | ||
| id: repro | ||
| attributes: | ||
| label: Steps to Reproduce | ||
| description: How can we see what you're seeing? Specific is terrific. | ||
| placeholder: |- | ||
| 1. What | ||
| 2. you | ||
| 3. did. | ||
| validations: | ||
| required: true | ||
| - type: textarea | ||
| id: expected | ||
| attributes: | ||
| label: Expected Result | ||
| validations: | ||
| required: true | ||
| - type: textarea | ||
| id: actual | ||
| attributes: | ||
| label: Actual Result | ||
| description: Logs? Screenshots? Yes, please. | ||
| validations: | ||
| required: true |
There was a problem hiding this comment.
Suggested change
| - type: textarea | |
| id: repro | |
| attributes: | |
| label: Steps to Reproduce | |
| description: How can we see what you're seeing? Specific is terrific. | |
| placeholder: |- | |
| 1. What | |
| 2. you | |
| 3. did. | |
| validations: | |
| required: true | |
| - type: textarea | |
| id: expected | |
| attributes: | |
| label: Expected Result | |
| validations: | |
| required: true | |
| - type: textarea | |
| id: actual | |
| attributes: | |
| label: Actual Result | |
| description: Logs? Screenshots? Yes, please. | |
| validations: | |
| required: true | |
| - type: textarea | |
| id: actual | |
| attributes: | |
| label: Current Behavior | |
| description: Logs? Screenshots? Yes, please. | |
| validations: | |
| required: true | |
| - type: textarea | |
| id: expected | |
| attributes: | |
| label: Expected Behavior | |
| description: What _should_ be happening? | |
| validations: | |
| required: true | |
| - type: textarea | |
| id: repro | |
| attributes: | |
| label: Steps to Reproduce | |
| description: How can we see what you're seeing? Specific is terrific. Repro repos are even better. | |
| placeholder: |- | |
| 1. What | |
| 2. you | |
| 3. did. | |
| validations: | |
| required: true |
I switched the order because IMHO the most salient thing is what's actually going wrong.
There was a problem hiding this comment.
Thanks Katie.
I would say, all 3 things are important here. It is true that in different scenarios, one is more important than the other. This already follows a known pattern for bug reporting so I would like to keep it as it is.
.github/ISSUE_TEMPLATE/config.yml
Outdated
Comment on lines
1
to
5
| blank_issues_enabled: false | ||
| contact_links: | ||
| - name: Ask a question | ||
| url: https://github.com/getsentry/sentry-javascript/discussions | ||
| about: Ask questions and discuss with other community members |
There was a problem hiding this comment.
I agree with Steven here, that for the moment it's just easier to have everything be in one place (issues) rather than two (issues and discussions).
Instead I think we should have a template which matches the bug report but has an open-ended "Describe your issue" text box in place of actual/expected/repro.
There was a problem hiding this comment.
Cool with me. I will point this to issues atm and later make an template with the label question
| label: Problem Statement | ||
| description: A clear and concise description of what you want and what your use case is. | ||
| placeholder: |- | ||
| I want to make whirled peas, but Sentry doesn't blend. |
Co-authored-by: Katie Byers <[email protected]>
Co-authored-by: Katie Byers <[email protected]>
Co-authored-by: Katie Byers <[email protected]>
Co-authored-by: Katie Byers <[email protected]>
size-limit report
|
Co-authored-by: Katie Byers <[email protected]>
Co-authored-by: Katie Byers <[email protected]>
|
Please rebase this and we can merge! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add new Github issue forms to this repository