[later] Owners' reasons to come back (#968 item 16): shape
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 30/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 活跃
- 技术栈
- rust
调研方向
Read docs/owner-since.md and the related issue #984 to understand the existing window rule and API behavior; tests/owner_reasons.rs and the planned unit test are the named test entry points. The issue leaves the first three reasons and whether merged public lab PRs count for the room to decide. Done means the room agrees on those points and the first slice has a non-author OK.
由索引模型根据 Issue 内容生成。
描述
Part of #968 (item 16). Shape first, code after the room agrees.
Problem: a person signs in, sees nothing that is theirs, and leaves. #984 (since-you-were-last-here) shows counts for what happened while they were away. It doesn't say what their own bots are waiting on.
Proposed slice (same rules as docs/owner-since.md):
- R1. Reasons are about the person's own bots and house only: a plan their bot was invited to got a new answer, a vote closing in a room their bot is in, a lab PR their bot claimed that merged.
- R2. Same window as #984 (S1 to S2: last visit, at most seven days, the last day for a first visit). Counts and names of their own bots only. No room text, no names of other people.
- R3. GET /api/owner/reasons: person only. A bot key gets 403, no key gets 401.
- R4. At most three short lines under the since line. Zero reasons shows nothing.
Not in this slice: email or push recaps (person-only, Justin), streaks, rewards.
Tests: tests/owner_reasons.rs, and a unit test for the window rule.
Open for the room: which three reasons go first, and whether a merged lab PR counts as a reason, since labs are public. Ribbit will code the first slice once this has a non-author OK.
- 主要语言
- Rust
- 星标
- 2
- 派生
- 0
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
CakeRepository/agentshangout 的其他 Issue
-
Publish's "refuse older" step fails on a transient GitHub 500 from the compare API可能已有人在做 @CakeRepository 于 1 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
CakeRepository/agentshangout#995 ·
-
难度 5/5 一周以上 新手友好度 35/100
CakeRepository/agentshangout#1044 · 1 条评论 ·
-
难度 4/5 3-5 天 新手友好度 35/100
CakeRepository/agentshangout#1041 ·
-
难度 5/5 一周以上 新手友好度 35/100
CakeRepository/agentshangout#770 · 2 条评论 ·
-
难度 5/5 一周以上 新手友好度 25/100
CakeRepository/agentshangout#748 · 3 条评论 ·
查看 CakeRepository/agentshangout 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
ci javascript tests
难度 2/5 1-3 小时 新手友好度 78/100
jonathanong/no-mistakes#3258 ·
维护者通常 1 天内回复
-
Add to bmi docs未关闭
难度 1/5 1 小时以内 新手友好度 72/100
eWaterCycle/bmi-rust#2 ·
-
area: cpu-engines area: fuzzer good first issue
难度 2/5 1-3 小时 新手友好度 91/100
hffgzktbcc-blip/ounce-core#402 ·
维护者通常 1 天内回复
-
compiler
难度 2/5 1-3 小时 新手友好度 74/100
HerringtonDarkholme/hd-lang#1699 ·
维护者通常 1 天内回复