microsoft / microsoft/vscode-remote-try-node

Https://issuetraker.google.com/issues?

Open
#110 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
831
Forks
812
PR merge metrics
No merged PRs in 30d

Description

### Tasks

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

The issue contains only an incomplete external tracker URL and an empty task list; no file, test, or entry point is named. Verify whether the external reference is valid and obtain a concrete requested change before selecting a code path. Done cannot be defined from the supplied issue text.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
devtools
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
1/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.