microsoft / microsoft/vscode-remote-release

Remote Containers and VSCodium

Open
#1,925 11 comments 147 reactions 1 assignee View on GitHub

@chrisdias is already working on this.

Since Nov 30, 2019.

Dominant language
Dockerfile
Stars
4.2k
Forks
470
Avg merge
1d 1h
Merged PRs (30d)
1

Description

In https://github.com/microsoft/vscode-remote-release/issues/967 @kieferrm writes:

Right. But since when isn't VSCodium a "Visual Studio family product"? It's quite clear that it is, given that it's built off the VS Code source code. The differences are minimal and not relevant in this context. It's clearly a "Visual Studio family product".

So, can you please remove the restriction in this extension such that VSCodium can use it fully? There's no point in not letting users of VSCodium use it the same way that they would if they were running VS Code.

Again, the differences between these two builds of the VS Code source code are minimal and of a completely different nature than what is relevant to this extension - the two builds would use and communicate with the extension in the very same way, hence the differences in the builds aren't practically relevant to this extension at all.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.