Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

run with all passes failed still reports Approve with comments

未关闭
#55 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
冷清
技术栈
typescript
领域
ci-cd, cli

调研方向

从 ecr ci 入口开始,追踪失败的 review pass 如何转换为显示的 verdict、pull request 评论和进程退出状态。复现 issue 中描述的所有 pass 均失败的情况,然后验证不完整或低于阈值的 coverage 会产生一个不同的失败状态、非零退出码和红色的 CI check,而不是批准。

由索引模型根据 Issue 内容生成。

描述

Seen on 0.9.2. A run where every review pass failed (subscription session limit) still prints the verdict "AI code review — Approve with comments":

  terraform-safety: FAILED (You've hit your session limit · resets 1:50am)
  cross-repo-boundary: FAILED (...)
  cluster-scaling: FAILED (...)
  kubernetes-manifests: FAILED (...)
  infra-security: FAILED (...)
All review passes failed — reporting an incomplete review.
Token usage — input 0, output 0, cache read 0, cache write 0

AI code review — Approve with comments
no findings

⚠️ The AI review could not complete: every review pass failed or timed out, so these changes were effectively NOT reviewed.

The body does say "treat this as no review", but the headline is still an approve variant. In ecr ci that posts a PR comment that reads as a green light unless you read the fine print, and the check stays green. When all passes fail (or coverage drops below some threshold) the verdict should be a distinct failed/incomplete state, not approve, and ecr ci should exit non-zero so the CI check goes red.

主要语言
TypeScript
星标
4
派生
0
平均合并
2 天 11 小时
30 天内合并 PR
3

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

expo/code-review-cli 的其他 Issue

查看 expo/code-review-cli 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。