quarto-dev / quarto-dev/quarto
VS Code VISX install instructions and how to pre-test features or releases
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 645
- Forks
- 62
- Avg merge
- 17h 42m
- Merged PRs (30d)
- 13
Description
Hi, glad to see new code popping up in main, but I also get that this is a busy project with a lot of dev work bubbling under the surface. I was looking to find ways that non-devs could maybe help out in testing new releases, features and bugfixes before they make it to formal publication, in case that could support development effort.
-
the link in https://github.com/quarto-dev/quarto/tree/main/apps/vscode#installation to
[install] directly from a [VISX extension file (#visx-install)is dead -
are there any suggested ways that power users can bring a specific branch to their local VS code install to test the newer or fixed functionality before it has gone through your full formal release cycle?
Happy to know if there are indirect ways like this to contibute. Thanks
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the apps/vscode Installation section linked in the issue and check the VISX extension-file link. Confirm how users can install a branch build in VS Code for pre-release testing, then update the instructions so the link works and the testing path is clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- documentation, release, testing
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100