Project dashboard: pick back up, needs-you, and team pulse
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 30/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 活跃
- 技术栈
- typescript
- 领域
- full-stack
调研方向
Start with the tracking issue #6 and the linked TODO.md 'Port from old Ace' entry in githubnext/ace2@21ac3df, since this issue itself only names the three features (dashboard briefing, resume work, team pulse) without saying where or how. Then locate the existing dashboard/UI entry points in this TypeScript repo to see what surfaces they would extend. Done means a design or scope decision is recorded on the issue before code is written — treat this as an umbrella, not a first patch.
由索引模型根据 Issue 内容生成。
描述
Give the project dashboard a briefing, a list of work to pick back up, and a team pulse, built from data Ace now has. Old Ace had all three (clients/app/src/features/dashboard in githubnext/1111); the dashboard here (apps/app/src/dashboard.tsx) is only a composer for starting a channel.
What old Ace did
-
Pick back up: up to 10 ranked rows of PRs and issues for the viewer:
- PRs and issues that already have a channel and are relevant to the viewer;
- the viewer's draft PRs;
- the viewer's PRs;
- PRs waiting on the viewer's review;
- issues assigned to the viewer.
Each row says Continue (open the existing channel) or Start new (open a channel on it). PRs from forks with no channel were skipped.
-
Briefing: a short model-written summary for the time of day of the viewer's recent channels, PRs and issues (8 of each), with inline links to each item.
-
Team pulse: one model-written line per teammate for a recent activity window, with avatars. When the model failed, it fell back to deterministic summaries.
Data available now
| Need | Source |
|---|---|
Channels per project, with owner, name, summary, latest run outcome (ran), active, busy, archived and hosted |
Host listings (apps/host/src/protocol.ts Listing), for teammates too, through peers and the directory |
| Who's here and away, live | Project lobbies (#17) |
| Created, archived, renamed, moved, summarized and ran, pushed live | Lobby lifecycle events (#337) |
| Finished, failed and waiting runs | apps/app/src/attention.ts, run outcomes |
| A lane's PR and its checks | Details PR lookup (apps/host/src/github.ts pull), checks |
| Issues and PRs for the repository | The Issues and PRs views (apps/app/src/github.tsx), using the owner's gh |
| The issue or PR a channel was opened for | Open in a channel (#109, #28) |
Scope
- Pick back up: (#471; issues don't link to their channel yet, since nothing records which item a channel was opened for) old Ace's ranking over the project's channels, PRs and issues. Rows link to the channel already on the item, including teammates' (this is also #28's "show who's on it"), or offer Open in a channel.
- Needs you: (#471) channels whose last run failed or is waiting on the viewer, and PRs waiting on the viewer's review.
- Team pulse: (deterministic version in #471; the optional model summary is still open) per teammate, who's here (lobby), their active channels with summaries, and what finished since the viewer was last here. Start deterministic, from listings and lifecycle events. A model summary is optional and must fall back to the deterministic version.
- Briefing (optional, later): a short model-written paragraph over the same inputs, with linked references.
Constraints:
- GitHub reads use the local owner's
gh(protocol.ts), never a peer's account. - Nothing new is stored durably; this is derived from listings, lobbies and GitHub.
Tracked by #6. Related: #12, #28, #17.
- 主要语言
- TypeScript
- 星标
- 1
- 派生
- 0
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
githubnext/ace2 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 94/100
githubnext/ace2#487 ·
-
难度 2/5 1-3 小时 新手友好度 90/100
githubnext/ace2#486 ·
-
难度 2/5 1-3 小时 新手友好度 67/100
githubnext/ace2#459 ·
-
难度 1/5 1 小时以内 新手友好度 88/100
githubnext/ace2#437 ·
-
难度 4/5 3-5 天 新手友好度 35/100
githubnext/ace2#442 ·
相似的 Issue
-
bug priority: P2
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
wayfinder:task
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
-
bug customer-reported data-plane question Service Attention Storage
难度 2/5 1-3 小时 新手友好度 69/100
Azure/azure-rest-api-specs#47397 · 2 条评论 ·
维护者通常 1 天内回复
-
Claude thinking budget can shrink capped Haiku responses to 2,048 tokens可能已有人在做 @DavyMassoneto 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
diegosouzapw/OmniRoute#17109 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
paperclipai/paperclip#16785 ·
维护者通常 1 天内回复