Triaging code-server issues is done with the following issue filter:

This will show issues that:

1. Are open.
2. Have no assigned project.
3. Are notblocked or tagged for work byupstream (the VS Code core team).If an upstream issue is detrimental to the code-server experience we may fixit in our patch instead of waiting for the VS Code team to fix it. Someoneshould periodically go through these issues to see if they can be unblocked!
4. Are not labeledwaiting-for-info.
5. Are not extension requests.

Triage process

1. If an issue is a question/discussion, it should be converted into a GitHubdiscussion.
2. Otherwise, give the issue the appropriate labels (feel free to create newones if necessary). There are no hard and set rules for labels. We don't havemany so look through and see how they've been used throughout the repository.They all also have descriptions.
3. If more information is required, please ask the submitter and tag aswaiting-for-info and wait.
4. Finally, the issue should be moved into thecode-server project where wepick out issues to fix and track their progress.

We also usemilestones to trackwhat issues are planned/or were closed for what release.