You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use this tool to assign and/or label a GitHub issue.
2
2
3
-
You can assign the following users:
4
-
- thdxr
5
-
- adamdotdevin
6
-
- fwang
7
-
- jayair
8
-
- kommander
9
-
- rekram1-node
3
+
Choose labels and assignee using the current triage policy and ownership rules.
4
+
Pick the most fitting labels for the issue and assign one owner.
10
5
11
-
12
-
You can use the following labels:
13
-
- nix
14
-
- opentui
15
-
- perf
16
-
- web
17
-
- zen
18
-
- docs
19
-
20
-
Always try to assign an issue, if in doubt, assign rekram1-node to it.
21
-
22
-
## Breakdown of responsibilities:
23
-
24
-
### thdxr
25
-
26
-
Dax is responsible for managing core parts of the application, for large feature requests, api changes, or things that require significant changes to the codebase assign him.
27
-
28
-
This relates to OpenCode server primarily but has overlap with just about anything
29
-
30
-
### adamdotdevin
31
-
32
-
Adam is responsible for managing the Desktop/Web app. If there is an issue relating to the desktop app or `opencode web` command. Assign him.
33
-
34
-
35
-
### fwang
36
-
37
-
Frank is responsible for managing Zen, if you see complaints about OpenCode Zen, maybe it's the dashboard, the model quality, billing issues, etc. Assign him to the issue.
38
-
39
-
### jayair
40
-
41
-
Jay is responsible for documentation. If there is an issue relating to documentation assign him.
42
-
43
-
### kommander
44
-
45
-
Sebastian is responsible for managing an OpenTUI (a library for building terminal user interfaces). OpenCode's TUI is built with OpenTUI. If there are issues about:
46
-
- random characters on screen
47
-
- keybinds not working on different terminals
48
-
- general terminal stuff
49
-
Then assign the issue to Him.
50
-
51
-
### rekram1-node
52
-
53
-
ALL BUGS SHOULD BE assigned to rekram1-node unless they have the `opentui` label.
54
-
55
-
Assign Aiden to an issue as a catch all, if you can't assign anyone else. Most of the time this will be bugs/polish things.
56
-
If no one else makes sense to assign, assign rekram1-node to it.
57
-
58
-
Always assign to aiden if the issue mentions "acp", "zed", or model performance issues
59
-
60
-
## Breakdown of Labels:
61
-
62
-
### nix
63
-
64
-
Any issue that mentions nix, or nixos should have a nix label
65
-
66
-
### opentui
67
-
68
-
Anything relating to the TUI itself should have an opentui label
69
-
70
-
### perf
71
-
72
-
Anything related to slow performance, high ram, high cpu usage, or any other performance related issue should have a perf label
73
-
74
-
### desktop
75
-
76
-
Anything related to `opencode web` command or the desktop app should have a desktop label. Never add this label for anything terminal/tui related
77
-
78
-
### zen
79
-
80
-
Anything related to OpenCode Zen, billing, or model quality from Zen should have a zen label
81
-
82
-
### docs
83
-
84
-
Anything related to the documentation should have a docs label
85
-
86
-
### windows
87
-
88
-
Use for any issue that involves the windows OS
6
+
If unsure, choose the team/section with the most overlap with the issue and assign a member from that team at random.
0 commit comments