Board the SDK watch and monthly dependency-refresh issues with the GitHub App token
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
调研方向
Start with sdk-watch.yml, dependency-refresh.yml, and AGENTS.md, then compare the Dependabot sweep's App-token step and inspect the dependency on #2544. Verify how each workflow creates issues and boards them on board #28 without running a model in a write-capable job; done means both board when secrets exist, preserve current behavior without them, and update the documented "never boards" statements.
由索引模型根据 Issue 内容生成。
描述
Problem
Two of the repo's three issue-filing sweeps never board what they file, and AGENTS.md records why: no board credential exists.
- SDK watch (
sdk-watch.yml) files issues labeledv2+chore+dependencies, milestoned, never boarded. - Monthly dependency refresh (
dependency-refresh.yml) files its tracking issue, milestoned, never boarded.
Each arrives unboarded and waits for /issue-triage. During the v2.9.0 release, #2521 and #2522 (the SDK bumps) had no cards until triage placed them by hand.
Change
Once the GitHub App exists (#2544), give both workflows the same App-token step as the Dependabot sweep, and have each place its issue on board #28:
- the SDK watch at
Todowith a rubric-derived priority, or a stated standing default - the monthly refresh at
Todo/Low, or as decided
Keep each sweep's rule that no model runs in a write-capable job. In sdk-watch.yml the boarding belongs in the sweep or post job, never in analyze.
Acceptance
- Both sweeps board their issues when the App secrets are present, and degrade to today's behavior when absent
-
AGENTS.md's "never boards" statements are updated in the same change
Blocked on
#2544 (the GitHub App). Part of tracker #2543.
- 主要语言
- TypeScript
- 星标
- 11.1k
- 派生
- 1.5k
- 平均合并
- 4 小时 4 分钟
- 30 天内合并 PR
- 170
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
modelcontextprotocol/inspector 的其他 Issue
-
chore v2
难度 4/5 3-5 天 新手友好度 48/100
modelcontextprotocol/inspector#2715 ·
维护者通常 1 天内回复
-
enhancement v2
难度 5/5 一周以上 新手友好度 35/100
modelcontextprotocol/inspector#2705 ·
维护者通常 1 天内回复
-
bug v2
难度 5/5 一周以上 新手友好度 35/100
modelcontextprotocol/inspector#2672 · 1 条评论 ·
维护者通常 1 天内回复
-
docs: record retroactive DCO signoffs for the 10 unsigned commits on v2/main可能已有人在做 @olaservo 于 7 天前认领。 未关闭documentation v2
modelcontextprotocol/inspector#2617 · 2 条评论 · 已指派 2 人 ·
维护者通常 1 天内回复
-
blocked chore v2
难度 4/5 3-5 天 新手友好度 52/100
modelcontextprotocol/inspector#2547 · 1 条评论 ·
维护者通常 1 天内回复
查看 modelcontextprotocol/inspector 的全部 Issue
相似的 Issue
-
Add: VIVE TV未关闭approved check:passed streams:add
难度 1/5 1 小时以内 新手友好度 72/100
维护者通常 1 天内回复
-
bug needs-triage
难度 2/5 1-3 小时 新手友好度 62/100
Fission-AI/OpenSpec#2084 ·
维护者通常 2 天内回复
-
Contrib indemnité de départ à la retraite : faire le pont avec le simulateur sur la page générique未关闭P1
难度 2/5 1-3 小时 新手友好度 62/100
SocialGouv/code-du-travail-numerique#7561 ·
维护者通常 1 天内回复
-
beginner bug
难度 1/5 1 小时以内 新手友好度 88/100
hiero-ledger/hiero-sdk-js#4517 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 85/100
kubernetes-sigs/headlamp#7950 ·
维护者通常 3 天内回复