Add a structured triage pipeline to loop-audit
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 43/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- github-actions, typescript
调研方向
Start with the course’s jq filter and the annotation step used by the loop-audit triage pipeline; the issue does not name their file paths. Run the filter as written on a sample triage stream and compare its count with the low-confidence failures. Then test the escaping rules and the comma/colon claim, and verify a hostile-message annotation in a real GitHub Actions run; done means the count and annotation location are correct and the PR records the runs.
由索引模型根据 Issue 内容生成。
描述
Parent
#15
What to build
A repo owner can copy the structured triage pipeline from loop-audit and trust its output. The "needs human review" count equals the number of low-confidence failures. Each CI annotation lands on the right file and line, whatever its message contains.
This ticket needs a human because one annotation has to render in a real GitHub Actions run, on a repo the owner picks.
Acceptance criteria
- The course's
jqfilter, run as written on a sample triage stream, gives the wrong count. After the fix, which collects low-confidence failures into one array before counting, it gives the right count. The PR description records both runs. - The annotation step escapes
%,\r, and\nin the message, and,and:in property values, per GitHub's workflow-command rules. - The review's claim that commas and colons in the message also break annotations is tested. If it does not reproduce, it is dropped, and the PR gives the run that disproved it.
- One annotation with a hostile message renders on the right file and line in a GitHub Actions run.
- 主要语言
- TypeScript
- 星标
- 0
- 派生
- 0
- 平均合并
- 3 小时 33 分钟
- 30 天内合并 PR
- 13
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
gregogun/gstack 的其他 Issue
-
ready-for-agent
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
ready-for-agent
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
ready-for-agent
难度 3/5 1-2 天 新手友好度 56/100
维护者通常 1 天内回复
-
ready-for-agent
难度 3/5 1-2 天 新手友好度 72/100
维护者通常 1 天内回复
相似的 Issue
-
[Bug]: REST API URL starting with "http" but no scheme (e.g. httpbin.org/get) is not given an http:// prefix可能已有人在做 @ItsDeadlyProgrammer 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 68/100
appsmithorg/appsmith#42471 · 1 条评论 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
ehmpathy/rhachet-roles-bhrain#705 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
Status: Triage
难度 2/5 1-3 小时 新手友好度 76/100
mermaid-js/mermaid#8546 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
braintrustdata/braintrust-sdk-javascript#2659 ·
维护者通常 1 天内回复