|
1 | 1 | # Triage
|
2 | 2 |
|
| 3 | +## Filter |
| 4 | + |
3 | 5 | Triaging code-server issues is done with the following issue filter:
|
4 | 6 |
|
5 | 7 | ```
|
6 |
| -is:open no:project sort:created-asc -label:blocked -label:upstream |
| 8 | +is:issue is:open no:project sort:created-asc -label:blocked -label:upstream -label:waiting-for-info -label:extension-request |
7 | 9 | ```
|
8 | 10 |
|
9 |
| -We cannot work on any `blocked` or `upstream` issues as those are best handled by the |
10 |
| -VS Code team. However, in certain circumstances we may fix them only in code-server if |
11 |
| -necessary. |
| 11 | +This will show issues that: |
| 12 | + |
| 13 | +1. Are open. |
| 14 | +2. Have no assigned project. |
| 15 | +3. Are not `blocked` or tagged for work by `upstream` (VS Code core team) |
| 16 | + - If an upstream issue is detrimental to the code-server experience we may fix it in |
| 17 | + our patch instead of waiting for the VS Code team to fix it. |
| 18 | + - Someone should periodically go through these issues to see if they can be unblocked |
| 19 | + though! |
| 20 | +4. Are not in `waiting-for-info`. |
| 21 | +5. Are not extension requests. |
| 22 | + |
| 23 | +## Process |
12 | 24 |
|
13 |
| -The GitHub project where we manage all our actionable issues is at: |
14 |
| -https://github.com/cdr/code-server/projects/1 |
| 25 | +1. If an issue is a question/discussion it should be converted into a GitHub discussion. |
| 26 | +2. Next, give the issue the appropriate labels and feel free to create new ones if |
| 27 | + necessary. |
| 28 | + - There are no hard and set rules for labels. We don't have many so look through and |
| 29 | + see how they've been used throughout the repository. They all also have descriptions. |
| 30 | +3. If more information is required, please ask the submitter and tag as |
| 31 | + `waiting-for-info` and wait. |
| 32 | +4. Finally, the issue should be moved into the |
| 33 | + [code-server](https://github.com/cdr/code-server/projects/1) project where we pick |
| 34 | + out issues to fix and track their progress. |
15 | 35 |
|
16 |
| -Finally, we use milestones to track what issues are planned/or were closed for what release. |
17 |
| -https://github.com/cdr/code-server/milestones |
| 36 | +We also use [milestones](https://github.com/cdr/code-server/milestones) to track what |
| 37 | +issues are planned/or were closed for what release. |
0 commit comments