-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
chore: update bug issue template #417
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The change sounds good to me, although I've left some comments for improvement. 👍🏼
[suggest] Is it easier to enter to put the new field after the reproduction-steps
field?
- Write reproduction steps
- Paste a reproduction URL
- ...
Co-authored-by: Masafumi Koba <473530+ybiquitous@users.noreply.github.com>
Thank you for your review.
True, I think it's easier to put it after |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you. LGTM 👍🏼
attributes: | ||
label: Link to Minimal Reproducible Example | ||
description: | | ||
Create a minimal reproduction of the problem. **A minimal reproduction is required** so that others can help debug your issue. If a report is vague (e.g. just a generic error message) and has no reproduction, it may be closed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[suggest] How about emphasizing a reproduction URL like this, though it seems a bit too long? 🤔
Create a minimal reproduction of the problem. **A minimal reproduction is required** so that others can help debug your issue. If a report is vague (e.g. just a generic error message) and has no reproduction, it may be closed. | |
Provide a minimal reproduction URL like a GitHub repository or a StackBlitz project. **A minimal reproduction is required** so that others can help debug your issue. If a report is vague (e.g. just a generic error message) and has no reproduction, it may be closed. |
Seems better if a shorter description would be good (one sentence if possible), but I don't have any good idea... 😓 (feel free to ignore this suggestion)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jeddy3 Any ideas?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Off topic, but I'm afraid StackBlitz can't run vscode extensions, unlike GitHub Codespaces.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see. Indeed, StackBlitz doesn't support 3rd-party extensions.
It seems GitHub Codespaces deprecates public access, so a GitHub repository is most suitable as a reproduction environment.
Are they reproducible using the 3 specific fields:
If not, what extra specific information is missing? We can add a field(s) for that/those. We can close any (existing and new) issues that don't supply enough information to reproduce the issue by saying they can reopen the issue by providing more info or a MRE. That's what we do in the main Stylelint issue tracker. Having said that, I haven't touched this repo much so feel to merge this pull request if the change in it works best for you. |
I can't pinpoint the cause. I think using the configuration they provide will work fine in most cases.
I've had bad experiences before, so I don't want to communicate with users of this extension as much as possible. |
@ota-meshi Thanks for trying to maintain the repository! 😄 |
None.
This PR updates the bug issue template to require a reproduction repository to be provided.
Many of the currently open issues are not reproducible as no repositories have been provided to reproduce the issue.