Davor Cubranic

Following the README in the `examples/grpc` directory, I ran `bazel build :all`, but got the following error: ``` C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.29.30133\bin\HostX64\x64\cl.exe /nologo /DCOMPILER_MSVC /DNOMINMAX /D_WIN32_WINNT=0x0601 /D_CRT_SECURE_NO_DEPRECATE /D_CRT_SECURE_NO_WARNINGS /bigobj...

Update docs to use "scan for compilers" instead of "kits"

3

### Brief Issue Summary The [documentation page](https://github.com/microsoft/vscode-cmake-tools/blob/main/docs/kits.md#scan-for-kits) directs the user to run "Scan for Kits" from the command palette, but the actual command (in the current release of VSCode, v1.86.0,...

foreign_cc-produced shared library can't be found by dependent binaries at runtime

2

I can build external libraries using the `cmake` rule, but when I try to use them as a dependency of a `cc_test` or `cc_binary`, on Windows they build but fail...

The link to Storage is wrong

5

The link to "Storage" in the [docs root page](https://prometheus.io/docs/prometheus/latest/), leads to `https://prometheus.io/docs/prometheus/storage/` instead of `https://prometheus.io/docs/prometheus/latest/storage/` (note the missing "latest" segment), so following it gets a "Page not found" error.

Commit action first opens an editor on a non-existent file

3

A recent VSCode update also updated edamagit to v0.6.64, and now commit first opens a blank editor on a non-existent file apparently named from a concatenation of path segments (e.g.,...