Explain Decisions in the product: open vs settled, and creating one manually
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 半天
- 新手友好度
- 45/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
调研方向
The payload names no files or components, so start by finding where decisions are created and listed in the UI and whether an empty state or first-use hint already exists. Read #595 and #596 first, since they are linked and may already settle the wording or the label. Done means a short in-product explanation covers what a decision is, that open and settled decisions exist, and how to create one manually; whether to rename the label needs a maintainer decision.
由索引模型根据 Issue 内容生成。
描述
The name "decision" reads as "something already decided", so it's unclear that a decision can be open, and how to start one by hand.
I'm not sure I understand the decision primitive. From its name, I assume it's only for things that are already decided, or are there open decisions? I'm not sure how to invoke a decision — can I do that manually? A little bit of onboarding to what decisions are and how you use them might help here.
Expected: a short in-product explanation (empty state or first-use hint) covering what a decision is, that open and settled ones exist, and how to create one manually. Possibly reconsider the label.
Related: #595, #596
Assistant-workflow: inline
- 主要语言
- TypeScript
- 星标
- 406
- 派生
- 24
- 平均合并
- 12 小时 42 分钟
- 30 天内合并 PR
- 416
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
githubnext/chopin 的其他 Issue
-
documentation triage/human-response
难度 2/5 1-3 小时 新手友好度 74/100
githubnext/chopin#149 · 3 条评论 ·
维护者通常 1 天内回复
-
enhancement
难度 4/5 3-5 天 新手友好度 30/100
githubnext/chopin#596 ·
维护者通常 1 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 12/100
githubnext/chopin#595 ·
维护者通常 1 天内回复
-
enhancement triage/human-response
难度 4/5 3-5 天 新手友好度 55/100
githubnext/chopin#203 · 2 条评论 ·
维护者通常 1 天内回复
-
enhancement triage/human-response
难度 5/5 一周以上 新手友好度 35/100
githubnext/chopin#165 ·
维护者通常 1 天内回复
查看 githubnext/chopin 的全部 Issue
相似的 Issue
-
e2e-failure ready-to-code
难度 2/5 1-3 小时 新手友好度 68/100
redhat-developer/rhdh-plugin-export-overlays#4460 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 77/100
维护者通常 1 天内回复
-
docs(api): openapi.yaml still documents gif-tools optimize colors as 2-256 instead of 2, 4, 16, 256未关闭area: backend documentation priority: low
难度 2/5 1-3 小时 新手友好度 84/100
snapotter-hq/SnapOtter#2919 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 77/100
obsidianmd/pele#39 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复