Skip to content

Commit eeb3c24

Browse files
LslightlyJorropo
authored andcommitted
docs/contributing: add missing `
add missing ` in docs/contributing.md Change-Id: Id19f59177c3ec6f428adaf0a38f56486bd8d0837 GitHub-Last-Rev: 1a21ede GitHub-Pull-Request: #3711 Reviewed-on: https://go-review.googlesource.com/c/vscode-go/+/656935 kokoro-CI: kokoro <[email protected]> Reviewed-by: Hongxiang Jiang <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]> Reviewed-by: Madeline Kalil <[email protected]> Reviewed-by: Jorropo <[email protected]>
1 parent 4370329 commit eeb3c24

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/contributing.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,7 @@ When running them from terminal:
101101
You can supply environment variables (e.g. `MOCHA_GREP`) by modifying the launch configuration entry's `env` property.
102102
- `Launch Unit Tests`: runs unit tests in `test/unit` (same as `npm run unit-test`)
103103
- `Launch Extension Tests`: runs tests in `test/integration` directory (similar to `npm run test` but runs only tests under `test/integration` directory)
104-
- `Launch Extension Tests with Gopls`: runs tests in `test/gopls directory (similar to `npm run test` but runs only tests under `test/gopls` directory)
104+
- `Launch Extension Tests with Gopls`: runs tests in `test/gopls` directory (similar to `npm run test` but runs only tests under `test/gopls` directory)
105105
106106
When you want to filter tests while debugging, utilize the `MOCAH_GREP` environment variable discussed previously - i.e., set the environment variable in the `env` property of the launch configuration.
107107

0 commit comments

Comments
 (0)