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

verify pass reads the local checkout instead of the PR head tree

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

还没有人认领这个 Issue。

评估

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

调研方向

针对堆叠的 PR 29434-29439 重现 ecr review --pr <n> --stack-aware,然后跟踪 verify pass 如何在 checkout 与 materialized PR head tree 之间进行选择。完成的标准是:验证和 reviewer 始终检查固定的 PR head,包括 29436 中的 29434 等继承的提交,且不会静默回退到本地文件。

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

描述

Seen on 0.9.2 running ecr review --pr <n> --stack-aware locally against expo/universe (stacked PRs 29434-29439).

The verify pass (and sometimes reviewers) read the local checkout instead of the materialized PR head tree. Concrete cases:

On universe#29437 the verifier dropped two findings with "No env.production.yaml exists, only env.staging.yaml" and "mise.toml has no deploy:production task, line 41 hardcodes --vpc-connector=pipeline-staging". The PR adds exactly those files and changes that line. It was describing main, not the PR head.

On universe#29434 the verifier dropped a finding saying "production main.tf lines 32-36 list only 10.8.0.0/16, 172.22.0.0/18, 172.22.64.0/20, the 10.10.0.0/28 entry exists only in staging". The diff adds 10.10.0.0/28 to the production file.

On universe#29436 (stacked on 29434) the security agent reported the secret production__cf_logs_kafka as "only declared for staging" even though the head branch includes the 29434 commit that adds it to production.

In these runs the dropped findings happened to be wrong anyway, but a verifier reading the wrong tree will eventually drop a true finding for a false reason, and it already produced one artifact warning (the 29436 secret one). No "falling back to your checked-out files" warning was printed, so the fallback was either silent or the verify pass never got the pinned tree in the first place.

主要语言
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 摘要。