EYHN 9cdfeba9b4 docs: issue triaging document (#5071) ...

I would like to sort out our process for handling github issues. When we receive a issue, we should first triage it.

This PR contains the document about issue triaging.

reference:
[YouTrack issue states used in .NET tools team and their description](https://rider-support.jetbrains.com/hc/en-us/articles/360021572199-YouTrack-issue-states-used-in-NET-tools-team-and-their-description)
[vscode Issues Triaging](https://github.com/microsoft/vscode/wiki/Issues-Triaging)

2023-11-27 08:27:34 +00:00

..

contributing

chore: change default branch to canary (#4948)

2023-11-15 07:46:50 +00:00

building-desktop-client-app.md

refactor(infra): directory structure (#4615)

2023-10-18 15:30:08 +00:00

BUILDING.md

docs: change yarn version in BUILDING.md (#4811)

2023-11-02 03:56:02 +00:00

CODE_OF_CONDUCT.md

chore: move docs to folder

2023-02-06 17:13:39 +08:00

CONTRIBUTING.md

chore: change default branch to canary (#4948)

2023-11-15 07:46:50 +00:00

contributor-add.md

docs: add contributors

2023-01-13 14:31:05 +08:00

developing-server.md

refactor(infra): directory structure (#4615)

2023-10-18 15:30:08 +00:00

issue-triaging.md

docs: issue triaging document (#5071)

2023-11-27 08:27:34 +00:00

jobs.md

Update jobs.md

2023-05-16 15:35:23 +08:00

types-of-contributions.md

Update types-of-contributions.md

2023-01-31 13:56:43 +08:00