chore: add vscode extension to issue template links #5524
Merged
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.
Description
Some people are reporting vscode extension bugs here, but we probably want them to open the issue downstream first, so they go through the checklist.
For the template, I copied what Vite does for react/vue plugins:
https://github.com/vitejs/vite/blob/84299f30a7244e6885e41531ffe5c4b54c8b0ed7/.github/ISSUE_TEMPLATE/config.yml#L3-L8
EDIT: Ah, I thought this issue #5523 is about vscode extension, but it's actually about vscode debugger without extension. I guess it's still fine to have this link?
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
pnpm-lock.yaml
unless you introduce a new test example.Tests
pnpm test:ci
.Documentation
pnpm run docs
command.Changesets
feat:
,fix:
,perf:
,docs:
, orchore:
.