Skip to content

Update assets in contribution guide #1531

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Apr 30, 2025
Merged

Update assets in contribution guide #1531

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ If you'd like to return to using the released version of the extension you can u

Occasionally, pre-release builds will be published to the VS Code Marketplace. You can switch to the pre-release version by clicking on the `Switch to Pre-Release Version` button in the Extensions View:

![](docs/images/install-pre-release.png)
![](userdocs/userdocs.docc/install-pre-release.png)

Switching back to the release version can be done by clicking on the `Switch to Release Version` button.

Expand Down Expand Up @@ -101,7 +101,7 @@ Now you can run tests locally using either of the following methods:
- Using `npm run test` from your terminal
- You can also use `npm run unit-test` or `npm run integration-test` to specifically run the Unit Tests or Integration Tests respectively.

Tests can also be launched from the terminal with the `--coverage` flag to display converage information. For example:
Tests can also be launched from the terminal with the `--coverage` flag to display coverage information. For example:

```bash
npm run unit-test -- --coverage
Expand Down