simplify /feedback flow to one path and allow inline in CLI
- 主要語言
- Shell
- 星號
- 11.2k
- 分支
- 1.9k
- 平均合併
- 14 小時 16 分鐘
- 30 天內合併 PR
- 6
描述
1. please make the /feedback command more simple and streamlined with just one path for us to give feedback and you do the sorting on your end into whether it's a bug or a feature request. don't make me pick from those three options - it adds friction and the distinction is not clear to me and just add frustration to a moment when a user is already frustrated and trying to submit feedback.
FWIW these are the three options i see today when in the cli i use /feedback
- Submit a private feedback survey
- File a bug report (publicly visible)
- File a feature request (publicly visible)
2. the identity when i got redirected to the github issuses page in the browser was my EMU identity and that just would not work. error message was completely unhelpful, just dead end. because now i've spent the time to fill in all these boxes and can't submit anything. please make this easier to navigate so i'm not then troubleshooting the feedback.
3. allow us to just type feedback directly in the CLI without redirecting us to a webpage. or auto copy what we filled into CLI into the webpage if you need that formatting, but don't take me into that new UI. in fact i misunderstood the how the /feedback command works and just lost a bunch of time because i typed it in directly after /feedback {here] and that all just went into the ether 😭
貢獻指南
研究方向
Start at the /feedback command flow in the CLI and trace how it presents the three current choices and redirects to the GitHub issues page. Done means feedback follows one streamlined path, supports direct inline CLI entry or preserves the entered text for the webpage, and avoids the reported identity dead end.
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- github, shell
- 領域
- cli, developer-experience
- Issue 類型
- 功能
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 活躍度
- 冷清
- 描述清晰度
- 基本清楚
- 新手友好度
- 45/100