chore: update bug issue template

[ota-meshi]

Which issue, if any, is this issue related to?

None.

Is there anything in the PR that needs further explanation?

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.

[ybiquitous]

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?

1. Write reproduction steps
2. Paste a reproduction URL
3. ...

[ota-meshi]

Thank you for your review.

[suggest] Is it easier to enter to put the new field after the reproduction-steps field?

True, I think it's easier to put it after reproduction-steps, as you say:+1:. I moved it.

[ybiquitous]

Thank you. LGTM 👍🏼

[ybiquitous]

[suggest] How about emphasizing a reproduction URL like this, though it seems a bit too long? 🤔

Suggested change

	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)

[ybiquitous]

@jeddy3 Any ideas?

[ota-meshi]

Off topic, but I'm afraid StackBlitz can't run vscode extensions, unlike GitHub Codespaces.

[ybiquitous]

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.

[jeddy3]

Many of the currently open issues are not reproducible as no repositories have been provided to reproduce the issue.

Are they reproducible using the 3 specific fields:

• Code Snippet
• Stylelint Configuration
• Extension Configuration

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.

[ota-meshi]

If not, what extra specific information is missing?

I can't pinpoint the cause. I think using the configuration they provide will work fine in most cases.

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.

I've had bad experiences before, so I don't want to communicate with users of this extension as much as possible.
If I know the cause immediately, I can fix it or present a solution and close it.

[ybiquitous]

@ota-meshi Thanks for trying to maintain the repository! 😄
Honestly, I've not touched this repository much, but I'll help you if any.